Papers › Packed Levitated Marker for Entity and Relation Extraction

Packed Levitated Marker for Entity and Relation Extraction

13 Sep 2021ACL 2022 5arXiv:2109.06067archive 2025-07-28

Deming Ye, Yankai Lin, Peng Li, Maosong Sun

Recent entity and relation extraction works focus on investigating how to obtain a better span representation from the pre-trained encoder. However, a major limitation of existing works is that they ignore the interrelation between spans (pairs). In this work, we propose a novel span representation approach, named Packed Levitated Markers (PL-Marker), to consider the interrelation between the spans (pairs) by strategically packing the markers in the encoder. In particular, we propose a neighborhood-oriented packing strategy, which considers the neighbor spans integrally to better model the entity boundary information. Furthermore, for those more complicated span pair classification tasks, we design a subject-oriented packing strategy, which packs each subject and all its objects to model the interrelation between the same-subject span pairs. The experimental results show that, with the enhanced marker feature, our model advances baselines on six NER benchmarks, and obtains a 4.1%-4.3% strict relation F1 improvement with higher speed over previous state-of-the-art models on ACE04 and ACE05.

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 9 code samples: 8 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 9: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 6 ran (1 with no instrument failure; 5 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 6 samples that ran have no recorded date.

thunlp/pl-marker officialmentioned in papermentioned on GitHubpytorchMITSyntology: 8 samples, 6 ran (5 instrument-failed) · 2 unverified report
tomaarsen/spanmarkerner mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to ACL Anthology id 2024.findings-emnlp.785 (that paper's own run record: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

9 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
5ran · our draft was wrong
3unverified

Licence: 3 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from thunlp/pl-marker. 1 sample is listed last, in a group without a repository. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

thunlp/pl-marker official repository 8 samples, 6 ran (5 instrument-failed) · 2 unverified
swish in 258 papers
census: 14 implementations from 37 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
transformers/src/transformers/activations.py ran · our draft was wrong fingerprinted MIT (permissive) · 0f786c407fb1ee4c · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded
to_list in 62 papers run_levitatedpair.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 9df40357afea56cc · report fixture: signature tensor:Tensor/2/float · returned list · level recorded, date not recorded
gelu_new in 55 papers
census: 3 implementations from 7 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
transformers/src/transformers/activations.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 77601724cad03f95 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
get_doc_key in 9 papers conll.py ran · our draft was wrong fingerprinted MIT (permissive) · f300a33fe05fc609 · report fixture: signature doc_id:str/0/str, part:int/0/int · returned str · level recorded 2026-09-25
get_original_token preprocess_ontonotes.py ran · our draft was wrong fingerprinted MIT (permissive) · e54f1fe179178f6b · report fixture: signature token:str/0/str · returned str · level recorded 2026-09-25
normalize_word in 22 papers preprocess_ontonotes.py ran · our draft was wrong fingerprinted MIT (permissive) · ba4eb9ed094dc59e · report fixture: signature word:str/0/str, language:str/0/str · returned str · level recorded 2026-09-25
evaluate_conll in 8 papers conll.py unverified MIT (permissive) · 15f2da988c1b38ad · report
official_conll_eval in 8 papers conll.py unverified MIT (permissive) · b12f4137ab9599e7 · report
Repository not located 1 sample, 0 ran · 1 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
load_tf_weights_in_albert in 9 papers repository not located unverified licence of this copy not recorded · 0acb90d02eadd73f · report

Tasks

Joint Entity and Relation ExtractionNamed Entity Recognition (NER)Relation Extraction

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Joint Entity and Relation Extraction SciERC PL-Marker Cross Sentence Yes #1 of 11 Archive leaderboard report
Joint Entity and Relation Extraction SciERC PL-Marker Entity F1 69.9 #1 of 11 Archive leaderboard report
Joint Entity and Relation Extraction SciERC PL-Marker RE+ Micro F1 41.6 #1 of 11 Archive leaderboard report
Joint Entity and Relation Extraction SciERC PL-Marker Relation F1 53.2 #1 of 11 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2003 (English) PL-Marker F1 94.0 #7 of 73 Archive leaderboard report
Named Entity Recognition (NER) Few-NERD (SUP) PL-Marker F1-Measure 70.9 #1 of 6 Archive leaderboard report
Named Entity Recognition (NER) Few-NERD (SUP) PL-Marker Precision 71.2 #1 of 6 Archive leaderboard report
Named Entity Recognition (NER) Few-NERD (SUP) PL-Marker Recall 70.6 #1 of 6 Archive leaderboard report
Named Entity Recognition (NER) Ontonotes v5 (English) PL-Marker F1 91.9 #2 of 28 Archive leaderboard report
Named Entity Recognition (NER) Ontonotes v5 (English) PL-Marker Precision 92.0 #2 of 28 Archive leaderboard report
Named Entity Recognition (NER) Ontonotes v5 (English) PL-Marker Recall 91.7 #2 of 28 Archive leaderboard report
Relation Extraction ACE 2004 PL-Marker Cross Sentence Yes #1 of 11 Archive leaderboard report
Relation Extraction ACE 2004 PL-Marker NER Micro F1 90.4 #1 of 11 Archive leaderboard report
Relation Extraction ACE 2004 PL-Marker RE Micro F1 69.7 #1 of 11 Archive leaderboard report
Relation Extraction ACE 2004 PL-Marker RE+ Micro F1 66.5 #1 of 11 Archive leaderboard report
Relation Extraction ACE 2005 PL-Marker Cross Sentence Yes #2 of 30 Archive leaderboard report
Relation Extraction ACE 2005 PL-Marker NER Micro F1 91.1 #2 of 30 Archive leaderboard report
Relation Extraction ACE 2005 PL-Marker RE Micro F1 73.0 #2 of 30 Archive leaderboard report
Relation Extraction ACE 2005 PL-Marker RE+ Micro F1 71.1 #2 of 30 Archive leaderboard report
Relation Extraction ACE 2005 PL-Marker Sentence Encoder ALBERT #2 of 30 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Introduced by this paper: Packed Levitated Markers

Absolute Position EncodingsPacked Levitated MarkersPosition-Wise Feed-Forward LayerTransformer

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