Papers › Passage Re-ranking with BERT

Passage Re-ranking with BERT

13 Jan 2019arXiv:1901.04085archive 2025-07-28

Rodrigo Nogueira, Kyunghyun Cho

Recently, neural models pretrained on a language modeling task, such as ELMo (Peters et al., 2017), OpenAI GPT (Radford et al., 2018), and BERT (Devlin et al., 2018), have achieved impressive results on various natural language processing tasks such as question-answering and natural language inference. In this paper, we describe a simple re-implementation of BERT for query-based passage re-ranking. Our system is the state of the art on the TREC-CAR dataset and the top entry in the leaderboard of the MS MARCO passage retrieval task, outperforming the previous state of the art by 27% (relative) in MRR@10. The code to reproduce our results is available at https://github.com/nyu-dl/dl4marco-bert

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 13 code samples harvested from 1 repository linked to this paper: 11 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; 3 where Syntology's instrument failed) · 2 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: 13 samples from 1 repository, 11 ran (8 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.

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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

nyu-dl/dl4marco-bert officialmentioned in papermentioned on GitHubtfBSD-3-ClauseSyntology: 13 samples, 11 ran (3 instrument-failed) · 2 unverified report
airKlizz/MsMarco mentioned on GitHubtfSyntology: not harvested report
castorini/pygaggle mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Improving Passage Retrieval with Zero-Shot Question Generation (arXiv:2204.07496; that paper's own run record: 8 ran (of which 4 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 6 unverified); nothing checks that they implement this paper's method. report
lukevs/charity-explorer mentioned on GitHubpytorchSyntology: not harvested report
mrjleo/ranking-models mentioned on GitHubpytorchMITSyntology: not harvested report
yang-ze-kang/PassageReranking pytorchSyntology: not harvested 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

13 samples harvested: 11 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; 3 where Syntology's instrument failed) · 2 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.

3ran · our draft was wrong
8ran
2unverified

Licence: 2 of the 13 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 nyu-dl/dl4marco-bert. “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.

nyu-dl/dl4marco-bert official repository 13 samples, 11 ran (3 instrument-failed) · 2 unverified
NDCG metrics.py ran BSD-3-Clause (permissive) · 1e33e4465ad9760e · report fixture: signature gt:list/1/str, pred:list/1/str, use_graded_scores:bool/0/bool · returned float64 · level recorded 2026-09-25
average_precision in 38 papers metrics.py ran BSD-3-Clause (permissive) · 45e8829b47e5a1b7 · report fixture: signature gt:set/0/?, pred:list/1/int · returned float · level recorded 2026-09-25
convert_to_bert_input tokenization.py ran BSD-3-Clause (permissive) · 895873eb21616a05 · report fixture: signature text:str/0/str, max_seq_length:int/0/int, tokenizer:MockTokenizer/0/?, add_cls:bool/0/bool · returned list · level recorded 2026-09-25
convert_to_unicode in 40 papers tokenization.py ran · our draft was wrong fingerprinted BSD-3-Clause (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 modeling.py ran · our draft was wrong BSD-3-Clause (permissive) · 5681f7dd9b6e3679 · report fixture: signature activation_string:str/0/str · returned function · level recorded 2026-09-22
input_fn_builder in 13 papers run_msmarco.py ran BSD-3-Clause (permissive) · e010030ee57fe701 · report fixture: signature dataset_path:str/0/str, seq_length:int/0/int, is_training:bool/0/bool, max_eval_examples:int/0/int · returned function · level recorded 2026-09-25
input_fn_builder in 13 papers run_treccar.py ran BSD-3-Clause (permissive) · 9fbf56276f399498 · report fixture: signature dataset_path:str/0/str, seq_length:int/0/int, is_training:bool/0/bool, max_eval_examples:NoneType/0/? · returned function · level recorded 2026-09-25
load_qrels in 12 papers convert_treccar_to_tfrecord.py ran BSD-3-Clause (permissive) · 9eb250ad7f25c79e · report fixture: signature path:str/0/str · returned defaultdict · level recorded 2026-09-25
load_run in 15 papers convert_treccar_to_tfrecord.py ran BSD-3-Clause (permissive) · 86c70a8984ca78b7 · report fixture: signature path:str/0/str · returned OrderedDict · level recorded 2026-09-25
metrics in 21 papers metrics.py ran BSD-3-Clause (permissive) · 54573d73f899d22f · report fixture: signature gt:set/0/?, pred:list/1/str, metrics_map:list/1/str · returned ndarray · level recorded 2026-09-25
printable_text in 36 papers tokenization.py ran · our draft was wrong BSD-3-Clause (permissive) · 0e5615f8994003cf · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-26
gelu in 308 papers
census: 43 implementations from 74 papers, 6 distinct outputs on one shared input
modeling.py unverified BSD-3-Clause (permissive) · ecab128238ebf253 · report
get_assignment_map_from_checkpoint in 32 papers modeling.py unverified BSD-3-Clause (permissive) here; the stored copy is pointer only · 50958618b65e514e · report

Tasks

Language ModelingPassage Re-RankingPassage RetrievalRe-RankingRetrieval

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Passage Re-Ranking MS MARCO BERT + Small Training MRR 0.359 #3 of 4 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

AdamAttentionAttention DropoutBERTBPEBiLSTMCosine AnnealingDense ConnectionsDiscriminative Fine-TuningDropoutELMoGPTLSTMLayer NormalizationLinear LayerLinear Warmup With Cosine AnnealingLinear Warmup With Linear DecayMulti-Head AttentionResidual ConnectionSigmoid ActivationSoftmaxTanh ActivationWeight 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