Papers › Hierarchical Context Tagging for Utterance Rewriting

Hierarchical Context Tagging for Utterance Rewriting

22 Jun 2022arXiv:2206.11218archive 2025-07-28

Lisa Jin, Linfeng Song, Lifeng Jin, Dong Yu, Daniel Gildea

Utterance rewriting aims to recover coreferences and omitted information from the latest turn of a multi-turn dialogue. Recently, methods that tag rather than linearly generate sequences have proven stronger in both in- and out-of-domain rewriting settings. This is due to a tagger's smaller search space as it can only copy tokens from the dialogue context. However, these methods may suffer from low coverage when phrases that must be added to a source utterance cannot be covered by a single context span. This can occur in languages like English that introduce tokens such as prepositions into the rewrite for grammaticality. We propose a hierarchical context tagger (HCT) that mitigates this issue by predicting slotted rules (e.g., "besides_") whose slots are later filled with context spans. HCT (i) tags the source string with token-level edit actions and slotted rules and (ii) fills in the resulting rule slots with spans from the dialogue context. This rule tagging allows HCT to add out-of-context tokens and multiple spans at once; we further cluster the rules to truncate the long tail of the rule distribution. Experiments on several benchmarks show that HCT can outperform state-of-the-art rewriting systems by ~2 BLEU points.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 9 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 9 ran (3 with no instrument failure; 6 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

lisjin/hct officialmentioned in paperpytorchSyntology: 11 samples, 9 ran (6 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 9 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
3ran · our draft was wrong
3ran; the contract check could not run
2ran
2unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from lisjin/hct. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

lisjin/hct official repository 11 samples, 9 ran (6 instrument-failed) · 2 unverified
AdditiveAttention in 5 papers sequence_tagger.py ran · metamorphic tier: deterministic no licence file found · pointer only · ee60d968887966a5 · report fixture: returned AdditiveAttention · level recorded 2026-09-22
SingleHeadedAttention sequence_tagger.py ran no licence file found · pointer only · 357f740c6eb1b176 · report fixture: signature key:Tensor/3/float, query:Tensor/3/float, value:Tensor/3/float, mask:Tensor/3/bool, type:NoneType/0/? · returned Tensor · level recorded 2026-09-24
cls_loss sequence_tagger.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only · d4dd26450a2f7454 · report fixture: signature dist:Tensor/2/float, refs:Tensor/1/int, masks:Tensor/1/float · returned Tensor · level recorded 2026-09-22
convert_tokens_to_string sequence_tagger.py ran · our draft was wrong no licence file found · pointer only · 29eebbec9a89a241 · report fixture: signature tokens:list/1/str · returned str · level recorded 2026-09-22
filter_spans sequence_tagger.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed fingerprinted no licence file found · pointer only · 4aaa0f929ca5124c · report fixture: signature starts:list/1/int, ends:list/1/int, max_i:int/0/int, stop_i:int/0/int · returned tuple · level recorded 2026-09-22
get_sp_strs sequence_tagger.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 1c3729d7bdc24044 · report fixture: signature start_lst:list/1/int, end_lst:list/1/int, context_len:int/0/int · returned tuple · level recorded 2026-09-22
ilst2str sequence_tagger.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 396a1ab20565832e · report fixture: signature lst:list/1/int · returned str · level recorded 2026-09-22
safe_log in 27 papers
census: 5 implementations from 5 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
sequence_tagger.py ran · honoured contract fingerprinted no licence file found · pointer only · f4b113a24e219244 · report fixture: signature inp:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-22
sample_helper sequence_tagger.py ran · our draft was wrong fingerprinted no licence file found · pointer only · d0642373c95680b9 · report fixture: signature logits:Tensor/3/float, dim:int/0/int · returned tuple · level recorded 2026-09-22
BertForSequenceTagging sequence_tagger.py unverified no licence file found · pointer only · 42281a8c6cec7703 · report
SpanClassifier sequence_tagger.py unverified no licence file found · pointer only · 505d10716b0d62e4 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Hierarchical Context Tagging (HCT) (graph method: Hierarchical Context Tagging (HCT)). 12 bricks; individually on a fixture: 10 ran (of which 1 constructed an object rather than computing a result; 4 with no instrument failure: 2 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. BertForSequenceTagging entry · level 0 · unverified · 42281a8c6cec7703
  2. SpanClassifier helper · level 0 · unverified · 505d10716b0d62e4
  3. convert_tokens_to_string helper · level 1 · ran · our draft was wrong · 29eebbec9a89a241
  4. get_sp_strs helper · level 1 · ran; the contract check could not run (RAISES) · 1c3729d7bdc24044
  5. safe_log helper · level 1 · ran · honoured contract · f4b113a24e219244
  6. sample_helper helper · level 1 · ran · our draft was wrong · d0642373c95680b9
  7. SingleHeadedAttention model · level 1 · ran · 357f740c6eb1b176
  8. cls_loss helper · level 1 · ran; the contract check could not run (RAISES) · d4dd26450a2f7454
  9. filter_spans helper · level 1 · ran; the contract check could not run (RAISES) · 4aaa0f929ca5124c
  10. ilst2str helper · level 1 · ran · our draft was wrong · 396a1ab20565832e
  11. AdditiveAttention helper · level 1 · ran · ee60d968887966a5
  12. generate_relative_positions_matrix helper · level 1 · ran · honoured contract · 0732a6087209857f

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2206.11218") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

TAG

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections