Papers › Revealing the Importance of Semantic Retrieval for Machine Reading at Scale
Revealing the Importance of Semantic Retrieval for Machine Reading at Scale
Yixin Nie, Songhe Wang, Mohit Bansal
Machine Reading at Scale (MRS) is a challenging task in which a system is given an input query and is asked to produce a precise output by "reading" information from a large knowledge base. The task has gained popularity with its natural combination of information retrieval (IR) and machine comprehension (MC). Advancements in representation learning have led to separated progress in both IR and MC; however, very few studies have examined the relationship and combined design of retrieval and comprehension at different levels of granularity, for development of MRS systems. In this work, we give general guidelines on system design for MRS by proposing a simple yet effective pipeline system with special consideration on hierarchical semantic retrieval at both paragraph and sentence level, and their potential effects on the downstream task. The system is evaluated on both fact verification and open-domain multihop QA, achieving state-of-the-art results on the leaderboard test sets of both FEVER and HOTPOTQA. To further demonstrate the importance of semantic retrieval, we present ablation and analysis studies to quantify the contribution of neural retrieval modules at both paragraph-level and sentence-level, and illustrate that intermediate semantic retrieval modules are vital for not only effectively filtering upstream information and thus saving downstream computation, but also for shaping upstream data distribution and providing better data for downstream modeling. Code/data made publicly available at: https://github.com/easonnie/semanticRetrievalMRS
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="1909.08041")
Code
Syntology Ran 6 of 17 code samples harvested from 2 repositories linked to this paper; 11 have no recorded run. Of those that ran: 4 ran · honoured contract; 2 ran · our draft was wrong.
By repository: official repository: 4 samples from 1 repository, 4 ran; community (archive-listed): 13 samples from 1 repository, 2 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
17 samples harvested; 6 ran; 4 honoured the contract we drafted; 11 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 17 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; each sample names its own and says which. “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.
5e7db7ffb7a92c64 · report
2781a9591cbfdb33 · report
bacc307a6797cb32 · report
ba1043dff5ce07b8 · report
0f786c407fb1ee4c · report
40e9fee2e0b7e278 · report
292d77ea319f82b8 · report
d8f74d3b75b19f79 · report
019955faa9c53626 · report
7ba88a577b6a2d52 · report
41f0dc9c6108d5df · report
6d9943f9b30c55eb · report
1df66838eb1b9b17 · report
b1c91c9e3a3b88e4 · report
0a343f931a447c8e · report
e157daea0cea1f36 · report
d008fe75170fedde · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Question Answering | HotpotQA | SemanticRetrievalMRS | ANS-EM | 0.453 | #44 of 72 | Archive leaderboard | report |
| Question Answering | HotpotQA | SemanticRetrievalMRS | ANS-F1 | 0.573 | #44 of 72 | Archive leaderboard | report |
| Question Answering | HotpotQA | SemanticRetrievalMRS | JOINT-EM | 0.251 | #44 of 72 | Archive leaderboard | report |
| Question Answering | HotpotQA | SemanticRetrievalMRS | JOINT-F1 | 0.476 | #44 of 72 | Archive leaderboard | report |
| Question Answering | HotpotQA | SemanticRetrievalMRS | SUP-EM | 0.387 | #44 of 72 | Archive leaderboard | report |
| Question Answering | HotpotQA | SemanticRetrievalMRS | SUP-F1 | 0.708 | #44 of 72 | 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