Papers › Seq2seq is All You Need for Coreference Resolution

Seq2seq is All You Need for Coreference Resolution

20 Oct 2023arXiv:2310.13774archive 2025-07-28

Wenzheng Zhang, Sam Wiseman, Karl Stratos

Existing works on coreference resolution suggest that task-specific models are necessary to achieve state-of-the-art performance. In this work, we present compelling evidence that such models are not necessary. We finetune a pretrained seq2seq transformer to map an input document to a tagged sequence encoding the coreference annotation. Despite the extreme simplicity, our model outperforms or closely matches the best coreference systems in the literature on an array of datasets. We also propose an especially simple seq2seq approach that generates only tagged spans rather than the spans interleaved with the original text. Our analysis shows that the model size, the amount of supervision, and the choice of sequence representations are key factors in performance.

PaperPDFCodeCode Syntology ran

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 14 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 11 ran (10 with no instrument failure; 1 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

wenzhengzhang/seq2seqcoref officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 11 ran (1 instrument-failed) · 3 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

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

1ran · our draft was wrong
10ran
3unverified

Licence: 3 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from wenzhengzhang/seq2seqcoref. “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.

wenzhengzhang/seq2seqcoref official repository 14 samples, 11 ran (1 instrument-failed) · 3 unverified
b_cubed in 12 papers metrics.py ran MIT (permissive) here; the stored copy is pointer only · 2d71e2917845b6ac · report fixture: signature clusters:list/1/list, mention_to_gold:dict/0/? · returned tuple · level recorded 2026-09-24
extract_clusters utils.py ran MIT (permissive) · 1b30aee01d2ddc01 · report fixture: signature sentence:str/0/str, start_mention_token:str/0/str, end_mention_token:str/0/str, start_ent_token:str/0/str, end_ent_token:str/0/str, remove_singletons:bool/0/bool · returned list · level recorded 2026-09-24
f1 in 57 papers metrics.py ran MIT (permissive) here; the stored copy is pointer only · 5dc251a1bb16c94f · report fixture: signature p_num:int/0/int, p_den:int/0/int, r_num:int/0/int, r_den:int/0/int, beta:int/0/int · returned float · level recorded 2026-09-25
get_doc_key in 9 papers conll.py ran · our draft was wrong fingerprinted MIT (permissive) · f300a33fe05fc609 · report fixture: signature doc_id:str/0/str, part:int/0/int · returned str · level recorded 2026-09-25
get_document_predicts data.py ran MIT (permissive) · a44d03c78991db18 · report fixture: signature doc_preds:list/1/list · returned list · level recorded 2026-09-24
get_mention_to_clusters utils.py ran MIT (permissive) · a757f2a0602e2db4 · report fixture: signature clusters:list/1/list · returned dict · level recorded 2026-09-24
global_align alignment.py ran fingerprinted MIT (permissive) · b39bade2b5608136 · report fixture: signature input_ids:list/1/int, rec_ids:list/1/int · returned dict · level recorded 2026-09-24
load_data in 700 papers check_align.py ran MIT (permissive) · 5266adb6d2ffdcfc · report fixture: signature data_dir:str/0/str, tokenizer:MockTokenizer/0/? · returned tuple · level recorded 2026-09-24
match_score in 7 papers alignment.py ran fingerprinted MIT (permissive) · 2f6a512c201dda17 · report fixture: signature a:int/0/int, b:int/0/int · returned int · level recorded 2026-09-24
max_track alignment.py ran MIT (permissive) · 4fe53dfaad013950 · report fixture: signature m:int/0/int, x:int/0/int, y:int/0/int, mode:str/0/str · returned tuple · level recorded 2026-09-24
normalize_word in 22 papers data.py ran fingerprinted MIT (permissive) · 1dfbebba563fe3db · report fixture: signature word:str/0/str, use_br_dict:bool/0/bool · returned str · level recorded 2026-09-24
evaluate_conll in 8 papers conll.py unverified MIT (permissive) · 17c2f60d7aa60c4e · report
evaluate_documents in 5 papers metrics.py unverified MIT (permissive) here; the stored copy is pointer only · 44ea1242eeeb38ac · report
official_conll_eval in 8 papers conll.py unverified MIT (permissive) · 623bb0c122976d14 · report

Tasks

AllCoreference Resolutioncoreference-resolution

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

LSTMSeq2SeqSigmoid ActivationTanh Activation

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