Browse State-of-the-Art › Event Relation Extraction
Event Relation Extraction
9 papers with code · 0 benchmarks · 1 dataset archive 2025-07-28
To extract relations among events, such as event coreference, temporal, causal and subevent relations.
Description from the archive 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
1 dataset 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: 18 · with a code link: 9 · 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 18 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 18 of 18, 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.
-
28 Jul 2024 1 repository listedLarge Language Models (LLMs) have demonstrated proficiency in a wide array of natural language processing tasks.
-
15 Nov 2023 1 repository listedUnderstanding events in texts is a core objective of natural language understanding, which requires detecting event occurrences, extracting event arguments, and analyzing inter-event relationships.
-
13 Oct 2023 1 repository listedMore in detail, we first investigate the deficiencies of LLMs in logical reasoning across different tasks.
-
25 Sep 2023 1 repository listedEvent understanding aims at understanding the content and relationship of events within texts, which covers multiple complicated information extraction tasks: event detection, event argument extraction, and event…
-
23 May 2023 1 repository listed Syntology official (archive's flag): 3 ran · 3 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 3 samples that ran constructed an object rather than computing a result (of 4 harvested samples)Event-centric structured prediction involves predicting structured outputs of events.
-
14 Nov 2022 1 repository listedIt contains 103, 193 event coreference chains, 1, 216, 217 temporal relations, 57, 992 causal relations, and 15, 841 subevent relations, which is larger than existing datasets of all the ERE tasks by at least an order…
-
1 May 2022 1 repository listedTo understand a story with multiple events, it is important to capture the proper relations across these events.
-
2 Apr 2022 1 repository listedTo achieve this goal, our work addresses the problems of subevent relation extraction (SRE) and temporal event relation extraction (TRE) that aim to predict subevent and temporal relations between two given event…
-
16 Jun 2021 1 repository listedCurrent event-centric knowledge graphs highly rely on explicit connectives to mine relations between events.
-
MAQInstruct: Instruction-based Unified Event Relation Extraction6 Feb 2025 0 repositories listedExtracting event relations that deviate from known schemas has proven challenging for previous methods based on multi-class classification, MASK prediction, or prototype matching.
-
Event-Arguments Extraction Corpus and Modeling using BERT for Arabic30 Jul 2024 0 repositories listedEvent-argument extraction is a challenging task, particularly in Arabic due to sparse linguistic resources.
-
TacoERE: Cluster-aware Compression for Event Relation Extraction11 May 2024 0 repositories listedEvent relation extraction (ERE) is a critical and fundamental challenge for natural language processing.
-
Event Temporal Relation Extraction based on Retrieval-Augmented on LLMs22 Mar 2024 0 repositories listedEvent temporal relation (TempRel) is a primary subject of the event relation extraction task.
-
GraphERE: Jointly Multiple Event-Event Relation Extraction via Graph-Enhanced Event Embeddings19 Mar 2024 0 repositories listedEvents describe the state changes of entities.
-
ProtoEM: A Prototype-Enhanced Matching Framework for Event Relation Extraction22 Sep 2023 0 repositories listedEvent Relation Extraction (ERE) aims to extract multiple kinds of relations among events in texts.
-
Event-Event Relation Extraction using Probabilistic Box Embedding16 Nov 2021 0 repositories listedTo understand a story with multiple events, it is important to capture the proper relations across these events.
-
Joint Constrained Learning for Event-Event Relation Extraction13 Oct 2020 0 repositories listedUnderstanding natural language involves recognizing how multiple event mentions structurally and temporally interact with each other.
-
Long-Distance Time-Event Relation Extraction1 Oct 2013 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