Papers › Named Entity Recognition as Dependency Parsing

Named Entity Recognition as Dependency Parsing

14 May 2020ACL 2020 6arXiv:2005.07150archive 2025-07-28

Juntao Yu, Bernd Bohnet, Massimo Poesio

Named Entity Recognition (NER) is a fundamental task in Natural Language Processing, concerned with identifying spans of text expressing references to entities. NER research is often focused on flat entities only (flat NER), ignoring the fact that entity references can be nested, as in [Bank of [China]] (Finkel and Manning, 2009). In this paper, we use ideas from graph-based dependency parsing to provide our model a global view on the input via a biaffine model (Dozat and Manning, 2017). The biaffine model scores pairs of start and end tokens in a sentence which we use to explore all spans, so that the model is able to predict named entities accurately. We show that the model works well for both nested and flat NER through evaluation on 8 corpora and achieving SoTA performance on all of them, with accuracy gains of up to 2.2 percentage points.

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

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

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

juntaoy/biaffine-ner officialmentioned in papertfApache-2.0Syntology: 10 samples, 6 ran (3 instrument-failed) · 4 unverified 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.

Code Syntology ran Syntology

10 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 4 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
3ran · our draft was wrong
2ran
4unverified

Licence: 2 of the 10 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 juntaoy/biaffine-ner. “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.

juntaoy/biaffine-ner official repository 10 samples, 6 ran (3 instrument-failed) · 4 unverified
flatten in 178 papers
census: 4 implementations from 7 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
util.py ran · honoured contract Apache-2.0 (permissive) · 20922c79a0929bbf · report fixture: signature l:list/1/list · returned list · level recorded, date not recorded
convert_to_unicode in 40 papers extract_bert_features/tokenization.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 1923fc05163d207d · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-22
get_activation in 218 papers extract_bert_features/modeling.py ran · our draft was wrong Apache-2.0 (permissive) · 2dc172f4dc0c745c · report fixture: signature activation_string:str/0/str · returned function · level recorded 2026-09-22
input_fn_builder in 13 papers extract_bert_features/extract_features.py ran Apache-2.0 (permissive) · fb8d325e40dbff1b · report fixture: signature examples:list/1/SimpleExample, window_size:int/0/int, stride:int/0/int, tokenizer:SimpleTokenizer/0/? · returned function · level recorded 2026-09-25
mkdirs in 7 papers util.py ran Apache-2.0 (permissive) · e9675d534fa5b1ba · report fixture: signature path:str/0/str · returned str · level recorded 2026-09-25
printable_text in 36 papers extract_bert_features/tokenization.py ran · our draft was wrong Apache-2.0 (permissive) · 0e5615f8994003cf · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-26
get_assignment_map_from_checkpoint in 32 papers extract_bert_features/modeling.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · 50958618b65e514e · report
load_vocab in 107 papers extract_bert_features/tokenization.py unverified Apache-2.0 (permissive) · ff83ccc8b0b6462d · report
make_summary in 6 papers util.py unverified Apache-2.0 (permissive) · 304ac22fbc54657a · report

Tasks

Dependency ParsingNERNamed Entity RecognitionNamed Entity Recognition (NER)Nested Named Entity RecognitionSentencenamed-entity-recognition

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Named Entity Recognition (NER) ACE 2004 Biaffine-NER F1 86.7 #3 of 9 Archive leaderboard report
Named Entity Recognition (NER) ACE 2004 Biaffine-NER Multi-Task Supervision n #3 of 9 Archive leaderboard report
Named Entity Recognition (NER) ACE 2005 Biaffine-NER F1 85.4 #11 of 20 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2002 (Dutch) Biaffine-NER F1 93.7 #4 of 6 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2002 (Spanish) Biaffine-NER F1 90.3 #3 of 6 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2003 (English) Biaffine-NER F1 93.5 #19 of 73 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2003 (German) Biaffine-NER F1 86.4 #5 of 6 Archive leaderboard report
Named Entity Recognition (NER) CoNLL 2003 (German) Revised Biaffine-NER F1 90.3 #4 of 5 Archive leaderboard report
Named Entity Recognition (NER) GENIA Biaffine-NER F1 80.5 #2 of 14 Archive leaderboard report
Named Entity Recognition (NER) Ontonotes v5 (English) Biaffine-NER F1 91.3 #4 of 28 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.

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