Papers › Code and Named Entity Recognition in StackOverflow

Code and Named Entity Recognition in StackOverflow

4 May 2020ACL 2020 6arXiv:2005.01634archive 2025-07-28

Jeniya Tabassum, Mounica Maddela, Wei Xu, Alan Ritter

There is an increasing interest in studying natural language and computer code together, as large corpora of programming texts become readily available on the Internet. For example, StackOverflow currently has over 15 million programming related questions written by 8.5 million users. Meanwhile, there is still a lack of fundamental NLP techniques for identifying code tokens or software-related named entities that appear within natural language sentences. In this paper, we introduce a new named entity recognition (NER) corpus for the computer programming domain, consisting of 15,372 sentences annotated with 20 fine-grained entity types. We trained in-domain BERT representations (BERTOverflow) on 152 million sentences from StackOverflow, which lead to an absolute increase of +10 F-1 score over off-the-shelf BERT. We also present the SoftNER model which achieves an overall 79.10 F₁ score for code and named entity recognition on StackOverflow data. Our SoftNER model incorporates a context-independent code token classifier with corpus-level features to improve the BERT-based tagging model. Our code and data are available at: https://github.com/jeniyat/StackOverflowNER/

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

By repository: official repository: 9 samples from 1 repository, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 4 samples from 1 repository, 2 ran (0 with no instrument failure; 2 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jeniyat/StackOverflowNER officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 7 ran (0 instrument-failed) · 2 unverified report
taidnguyen/software_entity_recognition mentioned on GitHubpytorchSyntology: 4 samples, 2 ran (2 instrument-failed) · 2 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

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 0 violated, 4 with no contract checked; 2 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 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.

3ran · honoured contract
2ran · our draft was wrong
4ran
4unverified

Licence: 0 of the 13 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.

jeniyat/StackOverflowNER official repository 9 samples, 7 ran (0 instrument-failed) · 2 unverified
argmax in 23 papers code/Attentive_BiLSTM/model.py ran · honoured contract fingerprinted MIT (permissive) · d38f06bbd9f9c98c · report fixture: signature vec:Tensor/2/float · returned int · level recorded 2026-09-22
calcMetrics code/Attentive_BiLSTM/conlleval_py.py ran MIT (permissive) · 82ddeedc1532be36 · report fixture: signature TP:int/0/int, P:int/0/int, T:int/0/int, percent:bool/0/bool · returned tuple · level recorded 2026-09-25
endOfChunk code/Attentive_BiLSTM/conlleval_py.py ran MIT (permissive) · 5d56e08fc935df9b · report fixture: signature prevTag:str/0/str, tag:str/0/str, prevType:str/0/str, type_:str/0/str · returned bool · level recorded 2026-09-25
gaussian in 218 papers
census: 8 implementations from 9 papers, 8 distinct outputs across 4 buckets, one shared input per bucket
code/Attentive_BiLSTM/gaussian_binner.py ran fingerprinted MIT (permissive) · 43cd754556c221e1 · report fixture: signature diff:ndarray/1/float, sig:float/0/float · returned ndarray · level recorded 2026-09-25
prepare_sequence code/Attentive_BiLSTM/model.py ran · honoured contract MIT (permissive) · 66f180f39c43eeb5 · report fixture: signature seq:list/1/str, to_ix:dict/0/? · returned Tensor · level recorded 2026-09-22
startOfChunk code/Attentive_BiLSTM/conlleval_py.py ran MIT (permissive) · dacaea8c1a2f5f82 · report fixture: signature prevTag:str/0/str, tag:str/0/str, prevType:str/0/str, type_:str/0/str · returned bool · level recorded 2026-09-25
to_scalar in 6 papers code/Attentive_BiLSTM/model.py ran · honoured contract fingerprinted MIT (permissive) · ac476e734740149f · report fixture: signature var:Tensor/2/float · returned float · level recorded 2026-09-22
save_char_embed code/Attentive_BiLSTM/train_so.py unverified MIT (permissive) · c9fe7ba81ee0b5b0 · report
unicodeToAscii in 5 papers code/Attentive_BiLSTM/loader_so.py unverified MIT (permissive) · 13c5cea0c71aab3f · report
taidnguyen/software_entity_recognition community (archive-listed) 4 samples, 2 ran (2 instrument-failed) · 2 unverified
get_labels in 42 papers src/model_nll.py ran · our draft was wrong Apache-2.0 (permissive) · 8d492584c2bb879a · report fixture: signature path:str/0/str · returned list · level recorded 2026-09-22
kl_div in 22 papers
census: 6 implementations from 6 papers, 5 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 1 of 4, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32
src/model_nll.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 978e6ebd9602e13a · report fixture: signature p:Tensor/2/float, q:Tensor/2/float · returned Tensor · level recorded 2026-09-22
NERModel src/model_nll.py unverified Apache-2.0 (permissive) · e0b7dc33e0488f7e · report
NLLModel src/model_nll.py unverified Apache-2.0 (permissive) · 95421f07c3753c59 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for BERTOverflow (graph method: BERTOverflow). 4 bricks; individually on a fixture: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. NLLModel entry · level 0 · unverified · 95421f07c3753c59
  2. NERModel helper · level 0 · unverified · e0b7dc33e0488f7e
  3. kl_div helper · level 1 · ran · our draft was wrong · 978e6ebd9602e13a
  4. get_labels helper · level 1 · ran · our draft was wrong · 8d492584c2bb879a

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2005.01634") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

NERNamed Entity RecognitionNamed Entity Recognition (NER)named-entity-recognition

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AdamAttentionAttention DropoutBERTDense ConnectionsDropoutLayer NormalizationLinear LayerLinear Warmup With Linear DecayMulti-Head AttentionResidual ConnectionSoftmaxWeight DecayWordPiece

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