Papers › CEDR: Contextualized Embeddings for Document Ranking

CEDR: Contextualized Embeddings for Document Ranking

15 Apr 2019arXiv:1904.07094archive 2025-07-28

Sean MacAvaney, Andrew Yates, Arman Cohan, Nazli Goharian

Although considerable attention has been given to neural ranking architectures recently, far less attention has been paid to the term representations that are used as input to these models. In this work, we investigate how two pretrained contextualized language models (ELMo and BERT) can be utilized for ad-hoc document ranking. Through experiments on TREC benchmarks, we find that several existing neural ranking architectures can benefit from the additional context provided by contextualized language models. Furthermore, we propose a joint approach that incorporates BERT's classification vector into existing neural models and show that it outperforms state-of-the-art ad-hoc ranking baselines. We call this joint approach CEDR (Contextualized Embeddings for Document Ranking). We also address practical challenges in using these models for ranking, including the maximum input length imposed by BERT and runtime performance impacts of contextualized language models.

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 7 code samples harvested from 2 repositories linked to this paper: 5 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; 1 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

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

Georgetown-IR-Lab/cedr officialmentioned in papermentioned on GitHubpytorchMITSyntology: 6 samples, 4 ran (0 instrument-failed) · 2 unverified report
Georgetown-IR-Lab/contextualized-reps-for-ranking officialmentioned in papermentioned on GitHubpytorchMITSyntology: not harvested report
Crysitna/CEDR_tpu mentioned on GitHubpytorchMITSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
Georgetown-IR-Lab/curricula-neural-ir mentioned on GitHubSyntology: not harvested report
TikaToka/CapstoneSpring mentioned on GitHubpytorchSyntology: not harvested report
crystina-z/CEDR_tpu mentioned on GitHubpytorchMITSyntology: not harvested report
ssun32/clirmatrix_cedr mentioned on GitHubpytorchMITSyntology: 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.

Code Syntology ran Syntology

7 samples harvested: 5 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; 1 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.

1ran · our draft was wrong
4ran
2unverified

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

Georgetown-IR-Lab/cedr official repository 6 samples, 4 ran (0 instrument-failed) · 2 unverified
read_datafiles cedr/data.py ran MIT (permissive) · 0b0ad78a7bebbc0e · report fixture: signature files:list/1/StringIO · returned tuple · level recorded 2026-09-25
read_qrels_dict cedr/data.py ran MIT (permissive) · 870ed1f39049bc26 · report fixture: signature file:StringIO/0/? · returned dict · level recorded 2026-09-25
read_run_dict cedr/data.py ran MIT (permissive) · 025beb6eeb8f3e37 · report fixture: signature file:StringIO/0/? · returned dict · level recorded 2026-09-25
un_subbatch cedr/modeling_util.py ran MIT (permissive) here; the stored copy is pointer only · bb05ea380c1dec92 · report fixture: signature embed:Tensor/2/float, toks:Tensor/2/int, maxlen:int/0/int · returned Tensor · level recorded 2026-09-24
indri_doc_extractor cedr/extract_docs_from_index.py unverified MIT (permissive) · edba46a99a939d85 · report
lucene_doc_extractor cedr/extract_docs_from_index.py unverified MIT (permissive) · f4cf6112e0ec013c · report
Crysitna/CEDR_tpu community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
subbatch modeling_util.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · b2840eb2211dadb4 · report fixture: signature toks:Tensor/2/int, maxlen:int/0/int · returned tuple · level recorded 2026-09-24

Tasks

Ad-Hoc Information RetrievalDocument RankingGeneral Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Ad-Hoc Information Retrieval TREC Robust04 CEDR-KNRM P@20 0.4667 #3 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 CEDR-KNRM nDCG@20 0.5381 #3 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 Vanilla BERT P@20 0.4042 #8 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 Vanilla BERT nDCG@20 0.4541 #8 of 21 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 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