Browse State-of-the-Art › Medical Relation Extraction
Medical Relation Extraction
9 papers with code · 2 benchmarks · 5 datasets archive 2025-07-28
Biomedical relation extraction is the task of detecting and classifying semantic relationships from biomedical text.
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
2 leaderboard tables shown for this task, 2 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.
Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): CMeIE (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| DDI extraction 2013 corpus (2 rows) | BioLinkBERT (large) | LinkBERT: Pretraining Language Models with Document Links | code | Syntology official: harvested, nothing ran · 3 ran (of which 0 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) · 11 unverified | Compare |
| CMeIE (1 row) | RoBERTa-wwm-ext-large | CBLUE: A Chinese Biomedical Language Understanding Evaluation Benchmark | code | Syntology official (archive's flag): 11 ran · 11 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified | 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
5 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.
Papers archive 2025-07-28
archive papers tagged: 15 · with a code link: 9 · where Syntology ran a sample: 4 (4 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 (4 of 15 tagged: 4 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 15 of 15, 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.
-
25 Jan 2019 19 repositories listed Syntology official: no sample here; runs from other or unrecorded repositories · 15 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 1 honoured, 0 violated, 10 with no contract checked; 4 where Syntology's instrument failed) · 10 unverified (of 25 harvested samples) · 3 pointer-only (licence)Biomedical text mining is becoming increasingly important as the number of biomedical documents rapidly grows.
-
13 Jun 2019 4 repositories listed Syntology community repositories only · 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 2 harvested samples)
-
15 Jun 2021 2 repositories listed Syntology official (archive's flag): 11 ran · 11 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified (of 16 harvested samples) · 2 pointer-only (licence)Artificial Intelligence (AI), along with the recent progress in biomedical language understanding, is gradually changing medical practice.
-
29 Aug 2022 1 repository listedHowever, the quality of the 1-best dependency tree for medical texts produced by an out-of-domain parser is relatively limited so that the performance of medical relation extraction method may degenerate.
-
29 Mar 2022 1 repository listed Syntology official: harvested, nothing ran · 3 ran (of which 0 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) · 11 unverified (of 14 harvested samples)Language model (LM) pretraining can learn various knowledge from text corpora, helping downstream tasks.
-
11 Nov 2019 1 repository listedMedical relation extraction discovers relations between entity mentions in text, such as research articles.
-
26 Jun 2018 1 repository listedMining relationships between treatment(s) and medical problem(s) is vital in the biomedical domain.
-
28 Jan 2017 1 repository listedThe two models, AB-LSTM and Joint AB-LSTM also use attentive pooling in the output of Bi-LSTM layer to assign weights to features.
-
9 Jan 2017 1 repository listedCognitive computing systems require human labeled data for evaluation, and often for training.
-
Causal Tree Extraction from Medical Case Reports: A Novel Task for Experts-like Text Comprehension3 Mar 2025 0 repositories listedExtracting causal relationships from a medical case report is essential for comprehending the case, particularly its diagnostic process.
-
Contrast with Major Classifier Vectors for Federated Medical Relation Extraction with Heterogeneous Label Distribution13 Jan 2023 0 repositories listedFederated medical relation extraction enables multiple clients to train a deep network collaboratively without sharing their raw medical data.
-
2 Feb 2022 0 repositories listedThere is an increasing interest in developing artificial intelligence (AI) systems to process and interpret electronic health records (EHRs).
-
FedED: Federated Learning via Ensemble Distillation for Medical Relation Extraction1 Nov 2020 0 repositories listedUnlike other domains, medical texts are inevitably accompanied by private information, so sharing or copying these texts is strictly restricted.
-
31 Aug 2020 0 repositories listedJoint medical relation extraction refers to extracting triples, composed of entities and relations, from the medical text with a single model.
-
Medical Relation Extraction with Manifold Models1 Jun 2014 0 repositories listed
Syntology lines on 4 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