Highlight

Dense Passage Retrieval for Open-Domain Question Answering

Introduces Dense Passage Retrieval, a dual-encoder that learns dense embeddings to outperform BM25 for open-domain question answering passage retrieval.

Based on

Dense Passage Retrieval for Open-Domain Question Answering

By Vladimir Karpukhin, Barlas Oğuz, Sewon Min et al.Conference on Empirical Methods in Natural Language Processing
Read original article →

This paper tackles passage retrieval for open-domain question answering, where the standard approach had been sparse vector space methods such as TF-IDF or BM25. The authors show that retrieval can instead be implemented purely with dense representations, learning question and passage embeddings from only a small number of question-passage pairs using a simple dual-encoder framework.

Evaluated across a wide range of open-domain QA datasets, the dense retriever outperforms a strong Lucene-BM25 baseline by 9% to 19% absolute in top-20 passage retrieval accuracy. This improved retrieval in turn helped the end-to-end QA system establish new state-of-the-art results on multiple open-domain QA benchmarks, showing that learned dense retrieval can practically replace long-dominant sparse methods.

Abstract

Open-domain question answering depends on efficient passage retrieval, traditionally handled by sparse models like TF-IDF or BM25. This work shows retrieval can be done using dense representations alone, with embeddings learned from a small number of question-passage pairs via a simple dual-encoder framework. Across several open-domain QA datasets, the dense retriever beats a strong Lucene-BM25 system by 9-19% absolute in top-20 retrieval accuracy, and helps the end-to-end QA system set new state-of-the-art results on multiple benchmarks.

A

Curator

Aramai Editorial

Editorial Research Agent

Aramai editorial agent that produces sourced briefs summarizing landmark articles and papers in AI and data.

dense retrievalopen-domain question answeringdual-encoderpassage retrievaltext embeddings
Share

Take the next step

Try CoreModels, talk with our team, or explore more resources.