Papers › Bidirectional LSTM-CRF Models for Sequence Tagging

Bidirectional LSTM-CRF Models for Sequence Tagging

9 Aug 2015arXiv:1508.01991archive 2025-07-28

Zhiheng Huang, Wei Xu, Kai Yu

In this paper, we propose a variety of Long Short-Term Memory (LSTM) based models for sequence tagging. These models include LSTM networks, bidirectional LSTM (BI-LSTM) networks, LSTM with a Conditional Random Field (CRF) layer (LSTM-CRF) and bidirectional LSTM with a CRF layer (BI-LSTM-CRF). Our work is the first to apply a bidirectional LSTM CRF (denoted as BI-LSTM-CRF) model to NLP benchmark sequence tagging data sets. We show that the BI-LSTM-CRF model can efficiently use both past and future input features thanks to a bidirectional LSTM component. It can also use sentence level tag information thanks to a CRF layer. The BI-LSTM-CRF model can produce state of the art (or close to) accuracy on POS, chunking and NER data sets. In addition, it is robust and has less dependence on word embedding as compared to previous observations.

PaperPDFCodeCode 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 8 code samples harvested from 2 repositories linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 8 samples from 2 repositories, 8 ran (8 with no instrument failure; 0 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.

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

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

25 repositories listed; official and paper-mentioned ones first.

Akshayanti/supersense-sequence-labelling mentioned on GitHubSyntology: not harvested report
DimasDMM/diseases-ner mentioned on GitHubSyntology: not harvested report
GlassyWing/bi-lstm-crf mentioned on GitHubApache-2.0Syntology: not harvested report
HassanAzzam/Arabic-NER mentioned on GitHubtfSyntology: not harvested report
JZ-LIANG/CRF-LSTM-NER mentioned on GitHubtfSyntology: not harvested report
UcasLzz/CWS mentioned on GitHubtfSyntology: not harvested report
UcasLzz/ChineseWordSeg-POS mentioned on GitHubApache-2.0Syntology: not harvested report
akshay-gupta123/BI-LSTM-CRF_Tensorflow mentioned on GitHubtfSyntology: not harvested report
aonotas/deep-crf mentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to End-to-end Sequence Labeling via Bi-directional LSTM-CNNs-CRF (arXiv:1603.01354; that paper's own run record: 24 ran (of which 0 constructed an object rather than computing a result; 22 with no instrument failure: 2 honoured, 0 violated, 20 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
baiyang2464/chatbot-base-on-Knowledge-Graph mentioned on GitHubtfSyntology: not harvested report
determined22/zh-ner-tf mentioned on GitHubtfSyntology: not harvested report
epwalsh/pytorch-crf mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to End-to-end Sequence Labeling via Bi-directional LSTM-CNNs-CRF (arXiv:1603.01354; that paper's own run record: 24 ran (of which 0 constructed an object rather than computing a result; 22 with no instrument failure: 2 honoured, 0 violated, 20 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
guillaumegenthial/tf_ner mentioned on GitHubtfApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Neural Architectures for Named Entity Recognition (arXiv:1603.01360; that paper's own run record: 29 ran (of which 0 constructed an object rather than computing a result; 22 with no instrument failure: 2 honoured, 1 violated, 19 with no contract checked; 7 where Syntology's instrument failed) · 7 unverified); nothing checks that they implement this paper's method. report
gxzzz/bilstm-crf mentioned on GitHubpytorchSyntology: not harvested report
hazelnutsgz/Naive-LSTM-CRF mentioned on GitHubpytorchSyntology: not harvested report
jidasheng/bi-lstm-crf mentioned on GitHubpytorchMITSyntology: 4 samples, 4 ran (0 instrument-failed) · 0 unverified report
kyzhouhzau/CCLNER mentioned on GitHubtfSyntology: not harvested report
moejoe95/crf-vs-rnn-ner mentioned on GitHubSyntology: not harvested report
ngoquanghuy99/POS-Tagging-BiLSTM-CRF mentioned on GitHubtfMITSyntology: 4 samples, 4 ran (0 instrument-failed) · 0 unverified report
sarveshsparab/BiLSTMCRFSeqTag mentioned on GitHubtfSyntology: not harvested report
sumehta/bilstm_crf_extract mentioned on GitHubpytorchSyntology: not harvested report
zysite/post mentioned on GitHubpytorchMITSyntology: not harvested report
2023-MindSpore-1/ms-code-5 mindsporeSyntology: not harvested report
MindSpore-paper-code-3/code9 mindsporeSyntology: not harvested report
mindspore-ai/models mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to AdaBin: Improving Binary Neural Networks with Adaptive Binary Sets (arXiv:2208.08084; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 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

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

8ran

Licence: 0 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

jidasheng/bi-lstm-crf community (archive-listed) 4 samples, 4 ran (0 instrument-failed) · 0 unverified
arguments_filepath bi_lstm_crf/app/utils.py ran fingerprinted MIT (permissive) · 37cca9481c5cf8bc · report fixture: signature model_dir:str/0/str · returned str · level recorded 2026-09-26
load_json_file in 35 papers bi_lstm_crf/app/preprocessing/utils.py ran MIT (permissive) · 4224c7914f484bfc · report fixture: signature file_path:str/0/str · returned dict · level recorded 2026-09-26
log_sum_exp in 51 papers
census: 10 implementations from 12 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
bi_lstm_crf/model/crf.py ran fingerprinted MIT (permissive) · 270d6bd48a51f2ae · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-26
model_filepath bi_lstm_crf/app/utils.py ran fingerprinted MIT (permissive) · 2b53a6f0ec5f47e8 · report fixture: signature model_dir:str/0/str · returned str · level recorded 2026-09-26
ngoquanghuy99/POS-Tagging-BiLSTM-CRF community (archive-listed) 4 samples, 4 ran (0 instrument-failed) · 0 unverified
build_vocab in 36 papers build_vocabulary.py ran MIT (permissive) · fb8b6b45dbfda514 · report fixture: signature corpus_path:str/0/str · returned list · level recorded 2026-09-26
get_word_tag utils.py ran MIT (permissive) · 04343636ba9e4577 · report fixture: signature line:str/0/str, vocab:set/0/? · returned tuple · level recorded 2026-09-26
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
utils.py ran MIT (permissive) · 763097a5a92e92d6 · report fixture: signature vocab:set/0/?, tokens:list/1/str · returned tuple · level recorded 2026-09-26
processing utils.py ran MIT (permissive) · 112daf6361c8290f · report fixture: signature vocab:set/0/?, text:list/1/str · returned list · level recorded 2026-09-26

Tasks

ChunkingNamed Entity Recognition (NER)POSSentenceTAG

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Chunking Penn Treebank BI-LSTM-CRF (Senna) (ours) F1 score 94.46 #8 of 8 Archive leaderboard report
Named Entity Recognition (NER) FindVehicle BiLSTM-CRF F1 Score 49.5 #1 of 3 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

CRFLSTMSigmoid ActivationTanh Activation

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