Browse State-of-the-Art › Document-level Event Extraction
Document-level Event Extraction
17 papers with code · 1 benchmark · 2 datasets archive 2025-07-28
Benchmarks archive 2025-07-28
1 leaderboard table shown for this task, 1 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 |
|---|---|---|---|---|---|
| ChFinAnn (4 rows) | ReDEE | RAAT: Relation-Augmented Attention Transformer for Relation... | 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.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 32 · with a code link: 17 · where Syntology ran a sample: 1 (1 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 (1 of 32 tagged: 1 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 32 of 32, 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.
-
13 Nov 2024 2 repositories listedOur research shows that trigger effectiveness varies based on the extraction task's characteristics and data quality, with basic, automatically-generated triggers serving as a viable alternative to human-annotated ones.
-
1 Aug 2021 2 repositories listedWe argue that sentence-level extractors are ill-suited to the DEE task where event arguments always scatter across sentences and multiple events may co-exist in a document.
-
31 May 2021 2 repositories listedExisting methods are not effective due to two challenges of this task: a) the target event arguments are scattered across sentences; b) the correlation among events in a document is non-trivial to model.
-
16 Apr 2019 2 repositories listedMost existing event extraction (EE) methods merely extract event arguments within the sentence scope.
-
23 Jun 2024 1 repository listedDocument-level event extraction aims to extract structured event information from unstructured text.
-
18 Apr 2024 1 repository listedTo alleviate this problem, we propose CMNEE, a large-scale, document-level open-source Chinese Military News Event Extraction dataset.
-
10 Feb 2024 1 repository listedWe introduce event-keyed summarization (EKS), a novel task that marries traditional summarization and document-level event extraction, with the goal of generating a contextualized summary for a specific event, given a…
-
23 Oct 2023 1 repository listedThis work is the first to apply the probing paradigm to representations learned for document-level information extraction (IE).
-
6 Sep 2022 1 repository listedTo fill this gap, we present FewDocAE, a Few-Shot Document-Level Event Argument Extraction benchmark, based on the existing document-level event extraction dataset.
-
1 Jul 2022 1 repository listedEvent extraction aims to identify an event and then extract the arguments participating in the event.
-
7 Jun 2022 1 repository listedTo further leverage relation information, we introduce a separate event relation prediction task and adopt multi-task learning method to explicitly enhance event extraction performance.
-
30 Apr 2022 1 repository listedIn this paper, we focus on extracting event arguments from an entire document, which mainly faces two critical problems: a) the long-distance dependency between trigger and arguments over sentences; b) the distracting…
-
11 Dec 2021 1 repository listedMost previous studies of document-level event extraction mainly focus on building argument chains in an autoregressive way, which achieves a certain success but is inefficient in both training and inference.
-
16 Nov 2021 1 repository listedDocument-level event extraction (DEE) extracts structured information of events from a document.
-
16 Aug 2021 1 repository listedFinally, our system ranks No. 4 on the test set leader-board of this multi-format information extraction task, and its F1 scores for the subtasks of relation extraction, event extractions of sentence-level and…
-
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.
-
13 May 2020 1 repository listedFew works in the literature of event extraction have gone beyond individual sentences to make extraction decisions.
-
Document-Level Event Extraction with Definition-Driven ICL10 Aug 2024 0 repositories listedIn the field of Natural Language Processing (NLP), Large Language Models (LLMs) have shown great potential in document-level event extraction tasks, but existing methods face challenges in the design of prompts.
-
Type-aware Decoding via Explicitly Aggregating Event Information for Document-level Event Extraction16 Oct 2023 0 repositories listedDocument-level event extraction (DEE) faces two main challenges: arguments-scattering and multi-event.
-
Token-Event-Role Structure-based Multi-Channel Document-Level Event Extraction30 Jun 2023 0 repositories listedDocument-level event extraction is a long-standing challenging information retrieval problem involving a sequence of sub-tasks: entity extraction, event type judgment, and event type-specific multi-event extraction.
-
CLIO: Role-interactive Multi-event Head Attention Network for Document-level Event Extraction1 Oct 2022 0 repositories listedTransforming the large amounts of unstructured text on the Internet into structured event knowledge is a critical, yet unsolved goal of NLP, especially when addressing document-level text.
-
基于框架语义映射和类型感知的篇章事件抽取(Document-Level Event Extraction Based on Frame Semantic Mapping and Type Awareness)1 Oct 2022 0 repositories listed“篇章事件抽取是从给定的文本中识别其事件类型和事件论元。目前篇章事件普遍存在数据稀疏和多值论元耦合的问题。基于此,本文将汉语框架网(CFN)与中文篇章事件建立映射,同时引入滑窗机制和触发词释义改善了事件检测的数据稀疏问题;使用基于类型感知标签的多事件分离策略缓解了论元耦合问题。为了提升模型的鲁棒性,进一步引入对抗训练。本文提出的方法在DuEE-Fin和CCKS2021数据集上实验结果显著优于现有方法。”
-
Document-Level Event Extraction via Human-Like Reading Process7 Feb 2022 0 repositories listedDocument-level Event Extraction (DEE) is particularly tricky due to the two challenges it poses: scattering-arguments and multi-events.
-
Exploiting Coreference and Schema Structure for Document-level Event Extraction16 Jan 2022 0 repositories listedDocument-level event extraction (DEE) extracts structured information of events from a document.
-
Writing Style Aware Document-level Event Extraction10 Jan 2022 0 repositories listedEvent extraction, the technology that aims to automatically get the structural information from documents, has attracted more and more attention in many fields.
-
A Two-Stream AMR-enhanced Model for Document-level Event Argument Extraction17 Dec 2021 0 repositories listedMost previous studies aim at extracting events from a single sentence, while document-level event extraction still remains under-explored.
-
DocEE: A Large-Scale and Fine-grained Benchmark for Document-level Event Extraction16 Nov 2021 0 repositories listedEvent extraction aims to identify an event and then extract the arguments participating in the event.
-
Towards Focused and Connected Document-Level Event Extraction16 Nov 2021 0 repositories listedDocument-level event extraction (DEE) is indispensable when events are naturally described in the form of a document.
-
Exploring Sentence Community for Document-Level Event Extraction1 Nov 2021 0 repositories listedDocument-level event extraction is critical to various natural language processing tasks for providing structured information.
-
DocEE: A Large-Scale Dataset for Document-level Event Extraction17 Sep 2021 0 repositories listedEvent extraction (EE) is the task of identifying events and their types, along with the involved arguments.
-
Document-level Event Extraction with Efficient End-to-end Learning of Cross-event Dependencies24 Oct 2020 0 repositories listed
-
基于BERT的端到端中文篇章事件抽取(A BERT-based End-to-End Model for Chinese Document-level Event Extraction)1 Oct 2020 0 repositories listed
Syntology lines on 1 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