Papers › NPRF: A Neural Pseudo Relevance Feedback Framework for Ad-hoc Information Retrieval

NPRF: A Neural Pseudo Relevance Feedback Framework for Ad-hoc Information Retrieval

30 Oct 2018EMNLP 2018 10arXiv:1810.12936archive 2025-07-28

Canjia Li, Yingfei Sun, Ben He, Le Wang, Kai Hui, Andrew Yates, Le Sun, Jungang Xu

Pseudo-relevance feedback (PRF) is commonly used to boost the performance of traditional information retrieval (IR) models by using top-ranked documents to identify and weight new query terms, thereby reducing the effect of query-document vocabulary mismatches. While neural retrieval models have recently demonstrated strong results for ad-hoc retrieval, combining them with PRF is not straightforward due to incompatibilities between existing PRF approaches and neural architectures. To bridge this gap, we propose an end-to-end neural PRF framework that can be used with existing neural IR models by embedding different neural models as building blocks. Extensive experiments on two standard test collections confirm the effectiveness of the proposed NPRF framework in improving the performance of two state-of-the-art neural IR models.

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 6 code samples harvested from 1 repository linked to this paper: 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) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 6 samples from 1 repository, 4 ran (4 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.

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

ucasir/NPRF officialmentioned in papertfApache-2.0Syntology: 6 samples, 4 ran (0 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

6 samples harvested: 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) · 2 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.

4ran
2unverified

Licence: 0 of the 6 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 ucasir/NPRF. “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.

ucasir/NPRF official repository 6 samples, 4 ran (0 instrument-failed) · 2 unverified
get_word_vec preprocess/matrix.py ran Apache-2.0 (permissive) · e52e3b386be1d9cb · report fixture: signature word:str/0/str, embeddings:MockEmbeddings/0/?, OOV_dict:dict/0/? · returned ndarray · level recorded 2026-09-25
hist_from_matrix preprocess/matrix.py ran Apache-2.0 (permissive) · 8de864fea0ae24a8 · report fixture: signature text_maxlen:int/0/int, hist_size:int/0/int, sim_mat:ndarray/2/float · returned ndarray · level recorded 2026-09-25
update_qrels_relevance preprocess/prepare.py ran Apache-2.0 (permissive) · 54587c99f765d612 · report fixture: signature qrels_file:str/0/str, docno_map:dict/0/? · returned OrderedDict · level recorded 2026-09-25
update_res_relevance preprocess/prepare.py ran Apache-2.0 (permissive) · d4fdda7951e2c107 · report fixture: signature res_file:str/0/str, docno_map:dict/0/? · returned OrderedDict · level recorded 2026-09-25
rank_hinge_loss metrics/rank_losses.py unverified Apache-2.0 (permissive) · f8a68c601c679661 · report
update_qrels_from_res_and_qrels preprocess/prepare.py unverified Apache-2.0 (permissive) · 7986b7c47df8beb5 · report

Tasks

Ad-Hoc Information RetrievalInformation RetrievalRetrieval

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Ad-Hoc Information Retrieval TREC Robust04 NPRF-DRMM MAP 0.2904 #9 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 NPRF-DRMM P@20 0.4064 #9 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 NPRF-DRMM nDCG@20 0.4502 #9 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 NPRF-KNRM MAP 0.2846 #13 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 NPRF-KNRM P@20 0.3926 #13 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 NPRF-KNRM nDCG@20 0.4327 #13 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 KNRM MAP 0.2464 #16 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 KNRM P@20 0.3510 #16 of 21 Archive leaderboard report
Ad-Hoc Information Retrieval TREC Robust04 KNRM nDCG@20 0.3989 #16 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.

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