Browse State-of-the-Art › Dialogue Generation

Dialogue Generation

265 papers with code · 13 benchmarks · 34 datasets archive 2025-07-28

Natural Language Processing

Dialogue generation is the task of "understanding" natural language inputs - within natural language processing in order to produce output. The systems are usually intended for conversing with humans, for instance back and forth dialogue with a conversation agent like a chatbot. Some example benchmarks for this task (see others such as Natural Language Understanding) include FusedChat and Ubuntu DIalogue Corpus (UDC). Models can be evaluated via metrics such as BLEU, ROUGE, and METEOR albeit with challenges in terms of weak correlation with human judgement, that may be addressed by new ones like UnSupervised and Reference-free (USR) and Metric for automatic Unreferenced dialog evaluation (MaUde).

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

13 leaderboard tables shown for this task, 13 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. 10 shown of 13 until expanded.

Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): PG-19 (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
Persona-Chat (6 rows) LMEDR Learning to Memorize Entailment and Discourse Relations for... code — Compare
FusedChat (2 rows) Classification-based model Fusing task-oriented and open-domain dialogues in conversational agents code — Compare
Harry Potter Dialogue Dataset (2 rows) EVA Large Language Models Meet Harry Potter: A Bilingual Dataset for... code — Compare
Amazon-5 (1 row) mm Adversarial Learning for Neural Dialogue Generation code Syntology 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified Compare
CMU-DoG (1 row) ∞-former (Sticky memories) ∞-former: Infinite Memory Transformer code — Compare
PG-19 (1 row) ∞-former (Sticky memories + initialized GPT-2 Small) ∞-former: Infinite Memory Transformer code — Compare
Reddit (multi-ref) (1 row) SpaceFusion Jointly Optimizing Diversity and Relevance in Neural Response Generation — — Compare
Twitter Dialogue (Noun) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... code — Compare
Twitter Dialogue (Tense) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... code — Compare
Ubuntu Dialogue (Activity) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... code — Compare
Ubuntu Dialogue (Cmd) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... code — Compare
Ubuntu Dialogue (Entity) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... code — Compare
Ubuntu Dialogue (Tense) (1 row) MrRNN Act.-Ent. Multiresolution Recurrent Neural Networks: An Application to... 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

34 datasets whose archive record lists this task, ordered by the archive's paper count. 30 shown of 34 until expanded.

Subtasks archive 2025-07-28

1 subtask in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 606 · with a code link: 265 · where Syntology ran a sample: 59 (49 with a run with no instrument failure, 10 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (59 of 606 tagged: 49 with a run with no instrument failure, 10 where every run was a failure of Syntology's instrument)

Page 1 of 7: papers 1 to 100 of 606, 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. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 27 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each 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.

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