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
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.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1810.12936")
Code
Syntology Ran 0 of 6 code samples harvested from 1 repository linked to this paper; 6 have no recorded run.
By repository: official repository: 6 samples from 1 repository, 0 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
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; 0 ran; 0 honoured the contract we drafted; 6 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.
e52e3b386be1d9cb · report
8de864fea0ae24a8 · report
f8a68c601c679661 · report
7986b7c47df8beb5 · report
54587c99f765d612 · report
d4fdda7951e2c107 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| 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