Browse State-of-the-Art › Zero-shot Event Extraction
Zero-shot Event Extraction
4 papers with code · 0 benchmarks · 0 datasets archive 2025-07-28
Benchmarks archive 2025-07-28
No benchmark for this task in the archive.
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
No dataset record in the archive lists this task.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 11 · with a code link: 4 · where Syntology ran a sample: 2 (2 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 (2 of 11 tagged: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 11 of 11, 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.
-
1 Jun 2025 1 repository listedThis paper presents LEMONADE, a large-scale conflict event dataset comprising 39, 786 events across 20 languages and 171 countries, with extensive coverage of region-specific entities.
-
5 Oct 2023 1 repository listed Syntology official (archive's flag): 18 ran · 18 ran (of which 2 constructed an object rather than computing a result; 17 with no instrument failure: 0 honoured, 0 violated, 17 with no contract checked; 1 where Syntology's instrument failed) · 7 unverified (of 25 harvested samples)In this paper, we propose GoLLIE (Guideline-following Large Language Model for IE), a model able to improve zero-shot results on unseen IE tasks by virtue of being fine-tuned to comply with annotation guidelines.
-
9 Nov 2022 1 repository listedWe argue that using the static embedding of the event type name might not be enough because a single word could be ambiguous, and we need a sentence to define the type semantics accurately.
-
13 Apr 2021 1 repository listed Syntology official (archive's flag): 9 ran · 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 (of 11 harvested samples)On the task of argument extraction, we achieve an absolute gain of 7.
-
A Monte Carlo Language Model Pipeline for Zero-Shot Sociopolitical Event Extraction24 May 2023 0 repositories listedCurrent social science efforts automatically populate event databases of "who did what to whom?"
-
Massively Multi-Lingual Event Understanding: Extraction, Visualization, and Search17 May 2023 0 repositories listedIn this paper, we present ISI-Clear, a state-of-the-art, cross-lingual, zero-shot event extraction system and accompanying user interface for event visualization & search.
-
Improving Zero-Shot Event Extraction via Sentence Simplification6 Apr 2022 0 repositories listedThe success of sites such as ACLED and Our World in Data have demonstrated the massive utility of extracting events in structured formats from large volumes of textual data in the form of news, social media, blogs and…
-
Hybrid Semantic Type Representation for Zero-Shot Event Extraction16 Jan 2022 0 repositories listedEvent extraction is a significant task in natural language processing.
-
Query and Extract: Refining Event Extraction as Type-oriented Binary Decoding16 Nov 2021 0 repositories listedEvent extraction is typically modeled as a multi-class classification problem where both event types and argument roles are treated as atomic symbols.
-
Query and Extract: Refining Event Extraction as Type-oriented Binary Decoding14 Oct 2021 0 repositories listedEvent extraction is typically modeled as a multi-class classification problem where event types and argument roles are treated as atomic symbols.
-
Zero-shot Event Extraction via Transfer Learning: Challenges and Insights1 Aug 2021 0 repositories listedEvent extraction has long been a challenging task, addressed mostly with supervised methods that require expensive annotation and are not extensible to new event ontologies.
Syntology lines on 2 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