Papers › Document-Level Event Argument Extraction by Conditional Generation

Document-Level Event Argument Extraction by Conditional Generation

13 Apr 2021NAACL 2021 4arXiv:2104.05919archive 2025-07-28

Sha Li, Heng Ji, Jiawei Han

Event extraction has long been treated as a sentence-level task in the IE community. We argue that this setting does not match human information-seeking behavior and leads to incomplete and uninformative extraction results. We propose a document-level neural event argument extraction model by formulating the task as conditional generation following event templates. We also compile a new document-level event extraction benchmark dataset WikiEvents which includes complete event and coreference annotation. On the task of argument extraction, we achieve an absolute gain of 7.6% F1 and 5.7% F1 over the next best model on the RAMS and WikiEvents datasets respectively. On the more challenging task of informative argument extraction, which requires implicit coreference reasoning, we achieve a 9.3% F1 gain over the best baseline. To demonstrate the portability of our model, we also create the first end-to-end zero-shot event extraction framework and achieve 97% of fully supervised model's trigger extraction performance and 82% of the argument extraction performance given only access to 10 out of the 33 types on ACE.

PaperPDFConference PDFCodeCode 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 11 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

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

raspberryice/gen-arg officialmentioned in paperpytorchMITSyntology: 11 samples, 9 ran (0 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 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 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.

9ran
2unverified

Licence: 0 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 raspberryice/gen-arg. “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.

raspberryice/gen-arg official repository 11 samples, 9 ran (0 instrument-failed) · 2 unverified
check_coref src/genie/convert_gen_to_output.py ran MIT (permissive) · d29d3fecf016262c · report fixture: signature ex:dict/0/?, arg_span:tuple/1/int, gold_spans:list/1/tuple · returned tuple · level recorded 2026-09-25
check_pronoun src/genie/utils.py ran MIT (permissive) · 9ce6efac63b8483f · report fixture: signature text:str/0/str · returned bool · level recorded 2026-09-25
clean_mention src/genie/utils.py ran fingerprinted MIT (permissive) · cd97889fceb677b3 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-25
clean_span src/genie/pipeline_scorer.py ran MIT (permissive) · 0c5be628187d2af8 · report fixture: signature ex:dict/0/?, span:tuple/1/int · returned tuple · level recorded 2026-09-25
extract_args_from_template src/genie/pipeline_scorer.py ran MIT (permissive) · 311da0dc94aa39ef · report fixture: signature ex:dict/0/?, template:str/0/str, ontology_dict:dict/0/? · returned defaultdict · level recorded 2026-09-25
find_head viz/visualize_output_KAIROS.py ran MIT (permissive) · e45fdae8c3fc7fb0 · report fixture: signature arg_start:int/0/int, arg_end:int/0/int, doc:MockDoc/0/? · returned tuple · level recorded 2026-09-25
get_event_type src/genie/convert_gen_to_output.py ran MIT (permissive) · 2d97ed4e5c2db314 · report fixture: signature ex:dict/0/? · returned list · level recorded 2026-09-25
my_collate in 23 papers src/genie/data.py ran MIT (permissive) · de4450d072db3735 · report fixture: signature batch:list/1/dict · returned dict · level recorded 2026-09-25
safe_div in 29 papers src/genie/utils.py ran fingerprinted MIT (permissive) · ac4edaf53cf349f7 · report fixture: signature num:int/0/int, denom:int/0/int · returned float · level recorded 2026-09-25
extract_args_from_template src/genie/convert_gen_to_output.py unverified MIT (permissive) · d5490a17a01f72e4 · report
find_arg_span viz/visualize_output_KAIROS.py unverified MIT (permissive) · 47d4228f0f998334 · report

Tasks

Document-level Event ExtractionEvent Argument ExtractionEvent ExtractionSentenceZero-shot Event Extraction

Datasets

Introduced by this paper, per the archive.

WikiEvents

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