Browse State-of-the-Art › Dialogue Rewriting
Dialogue Rewriting
4 papers with code · 3 benchmarks · 2 datasets archive 2025-07-28
Benchmarks archive 2025-07-28
3 leaderboard tables shown for this task, 3 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| Multi-Rewrite (3 rows) | RUN+BERT | Incomplete Utterance Rewriting as Semantic Segmentation | code | — | Compare |
| CANARD (1 row) | SARG | SARG: A Novel Semi Autoregressive Generator for Multi-turn... | code | — | Compare |
| Rewrite (1 row) | RUN+BERT | Incomplete Utterance Rewriting as Semantic Segmentation | code | — | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
2 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Papers archive 2025-07-28
archive papers tagged: 7 · with a code link: 4 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 7 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 7 of 7, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
29 Dec 2020 1 repository listedThe task of dialogue rewriting aims to reconstruct the latest dialogue utterance by copying the missing content from the dialogue context.
-
28 Sep 2020 1 repository listedRecent years the task of incomplete utterance rewriting has raised a large attention.
-
4 Aug 2020 1 repository listedDialogue systems in open domain have achieved great success due to the easily obtained single-turn corpus and the development of deep learning, but the multi-turn scenario is still a challenge because of the frequent…
-
14 Jun 2019 1 repository listedTo properly train the utterance rewriter, we collect a new dataset with human annotations and introduce a Transformer-based utterance rewriting architecture using the pointer network.
-
Friend-training: Learning from Models of Different but Related Tasks31 Jan 2023 0 repositories listedCurrent self-training methods such as standard self-training, co-training, tri-training, and others often focus on improving model performance on a single task, utilizing differences in input features, model…
-
RAST: Domain-Robust Dialogue Rewriting as Sequence Tagging1 Nov 2021 0 repositories listedThe task of dialogue rewriting aims to reconstruct the latest dialogue utterance by copying the missing content from the dialogue context.
-
Semantic Role Labeling Guided Multi-turn Dialogue ReWriter3 Oct 2020 0 repositories listedFor multi-turn dialogue rewriting, the capacity of effectively modeling the linguistic knowledge in dialog context and getting rid of the noises is essential to improve its performance.
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