In plain words: Language models that look up outside information before answering are surveyed, covering how the search step, the model, and their connection work for both writing text and understanding it. Such systems make fewer made-up claims and handle specialized knowledge better, but struggle with search quality and computing cost.
Abstract · RAG and RAU: A Survey on Retrieval-Augmented Language Model in Natural Language Processing
Large Language Models (LLMs) have catalyzed significant advancements in Natural Language Processing (NLP), yet they encounter challenges such as hallucination and the need for domain-specific knowledge. To mitigate these, recent methodologies have integrated information retrieved from external resources with LLMs, substantially enhancing their performance across NLP tasks. This survey paper addresses the absence of a comprehensive overview on Retrieval-Augmented Language Models (RALMs), both Retrieval-Augmented Generation (RAG) and Retrieval-Augmented Understanding (RAU), providing an in-depth examination of their paradigm, evolution, taxonomy, and applications. The paper discusses the essential components of RALMs, including Retrievers, Language Models, and Augmentations, and how their interactions lead to diverse model structures and applications. RALMs demonstrate utility in a spectrum of tasks, from translation and dialogue systems to knowledge-intensive applications. The survey includes several evaluation methods of RALMs, emphasizing the importance of robustness, accuracy, and relevance in their assessment. It also acknowledges the limitations of RALMs, particularly in retrieval quality and computational efficiency, offering directions for future research. In conclusion, this survey aims to offer a structured insight into RALMs, their potential, and the avenues for their future development in NLP. The paper is supplemented with a Github Repository containing the surveyed works and resources for further study: https://github.com/2471023025/RALM_Survey.
Yucheng Hu, Yuxing Lu
arXiv:2404.19543 · cs.CL, cs.AI · submitted Apr 30, 2024 · updated Jun 29, 2025
abstract · pdf · html · 30 pages, 7 figures. Draft version 1
1. Quality control. What documents to include?
2. Timing. When to query?
3. Pre & post processing. Improve LLM outputs based on retrieved data.
4. End to end training. Expensive, and data intensive but possibly the best long-term approach.
5. Controller. An interesting idea with similarities to Reinforcement Learning.
I wonder what are your thoughts. Which one is most promising? What has been your experience when building RAG apps? Also, is RAG the leading architecture for building applications?