RAG-Fusion: a New Take on Retrieval-Augmented Generation

Zackary Rackauckas
1/31/2024
cs.IRcs.LG

No confident code implementation found for this paper. 8 possible matches can be shown below.

Abstract

Infineon has identified a need for engineers, account managers, and customers to rapidly obtain product information. This problem is traditionally addressed with retrieval-augmented generation (RAG) chatbots, but in this study, I evaluated the use of the newly popularized RAG-Fusion method. RAG-Fusion combines RAG and reciprocal rank fusion (RRF) by generating multiple queries, reranking them with reciprocal scores and fusing the documents and scores. Through manually evaluating answers on accuracy, relevance, and comprehensiveness, I found that RAG-Fusion was able to provide accurate and comprehensive answers due to the generated queries contextualizing the original query from various perspectives. However, some answers strayed off topic when the generated queries' relevance to the original query is insufficient. This research marks significant progress in artificial intelligence (AI) and natural language processing (NLP) applications and demonstrates transformations in a global and multi-industry context.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. 8 weaker matches are hidden by default — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{rackauckas2024ragfusion,
  title  = {RAG-Fusion: a New Take on Retrieval-Augmented Generation},
  author = {Zackary Rackauckas},
  year   = {2024},
  eprint = {2402.03367},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2402.03367v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2402.03367.svg)](https://codeofpaper.com/paper/2402.03367)

Discussion