XRAG: eXamining the Core - Benchmarking Foundational Components in Advanced Retrieval-Augmented Generation
December 20, 2024
Retrieval-augmented generation (RAG) synergizes the retrieval of pertinent database with the generative capabilities of Large Language Models (LLMs), ensuring that the generated output is contextually relevant but also accurate and current. We introduce XRAG, an open-source, modular codebase that facilitates exhaustive evaluation of the performance of foundational components of advanced RAG modules. These components are categorized into four core phases: pre-retrieval, retrieval, post-retrieval, and generation. We systematically analyze them across reconfigured datasets, providing a comprehensive benchmark for their effectiveness. These components can be combined in different ways through an orchestrator, of which there are five types: sequential, conditional, iterative, parallel, and hybrid. Our work thoroughly evaluates the performance of advanced core components in RAG systems, offering actionable insights for optimizing RAG architectures in dataset-driven AI applications.
Database, Retrieval-Augmented Generation, Evaluation, Benchmark, Data Management
Retrieval-Augmented Generation (RAG) [1]–[8] represents a pivotal strategy in Q&A tasks, demonstrating enhanced performance by delivering more informative and accurate answers compared to relying solely on large language models (LLMs). The efficacy of basic RAG systems [9], [10] is contingent depends on the seamless operation of four core components: pre-retrieval, retrieval, post-retrieval, and generation. The pre-retrieval stage indexes the corpus and reforms queries for efficient retrieval. The retrieval stage focuses on identifying and extracting documents relevant to a given query. The post-retrieval stage refines, summarizes, or compacts information to ensure contextual clarity. Finally, the generation stage employs the LLM to produce responses. In naive RAG systems, these stages are executed in a sequential manner. However, when dealing with complex retrieval scenarios, naive RAG often suffers from inefficiency and incomplete retrieval. Therefore, advanced RAG systems have optimized the retrieval process instead of sequential. Five RAG processes are as follows: sequential, conditional, iterative, parallel, and hybrid. These stages and processes critically influence output quality, highlighting the RAG framework’s interdependence.
| RAG Library | Mod.Dsgn | Fair.Comp | Unif.Data | Mod.Eva | ConR | ConG | CogL |
|---|---|---|---|---|---|---|---|
| LangChain [12] | 0 | 0 | 0 | ||||
| LlamaIndex [13] | 6 | 0 | 7 | ||||
| FastRAG [14] | 0 | 0 | 0 | ||||
| RALLE [15] | 0 | 0 | 0 | ||||
| LocalRQA [16] | 3 | 2 | 1 | ||||
| AutoRAG [17] | 6 | 5 | 4 | ||||
| FlashRAG [18] | 4 | 5 | 0 | ||||
| RAGLAB [11] | 0 | 4 | 0 | ||||
| sec:XRAG (ours) | \(\textcolor{c5}{\textbf{7}^{ u}}\) | \(\textcolor{c5}{\textbf{10}^{ u}}\) | \(\textcolor{c5}{\textbf{23}^{ u}}\) | ||||
In real-world applications characterized by complex dataset structures, existing RAG frameworks exhibit significant limitations. Modular RAG toolkits like LangChain [12] and LlamaIndex [13] are typically cumbersome, making adaptation to new data challenging and validating or optimizing innovative methods inconvenient. Efficient RAG Frameworks like FastRAG [14], RALLE [15], AutoRAG [17], and LocalRQA [16] require users to independently reproduce published algorithms and offer limited component options, restricting the flexibility of RAG systems despite modular designs. In module evaluation tasks, FlashRAG [18] lacks uniformity in fundamental evaluation components, such as random seeds, generators, retrievers, and instructions, which hinders result comparability. RAGLAB [11], despite offering a fair experimental setup, lacks comprehensive evaluation strategies for assessing individual RAG components. Although ongoing efforts address these challenges through modular RAG processes (e.g., retrieval engines and generative agents), an implicit gap persists in the comparative performance evaluations of these advanced RAG modules within the overall RAG workflow. Comprehensive assessments of these modules are notably absent, making it difficult for researchers to evaluate their approaches in consistent experimental conditions.
To address the above issues, we concentrate on the core components of advanced RAG modules and the orchestrators of agentic RAG, conducting comprehensive experiments. We introduce XRAG 1, an open-source, modular codebase designed to evaluate foundational components of advanced RAG modules comprehensively. XRAG offers four principal capabilities:
Modular RAG Architecture: Fine-Grained Comparative Analysis. Extensive experiments are conducted on the advanced RAG modules in four stages: pre-retrieval, retrieval, post-retrieval, and generation. The core components cover three query rewriting strategies, six retrieval units, three post-processing techniques, and LLM generators from different vendors — OpenAI, Meta, and DeepSeek. XRAG provides an in-depth understanding of the capabilities of RAG components.
Agentic RAG Process: Multi-Orchestrator Integration and Workflow Design. The XRAG architecture incorporates five orchestrators: sequential, conditional, iterative, parallel, and hybrid. It provides a streamlined framework to flexibly orchestrating agentic RAG processes and integrate advanced RAG modules. Furthermore, to guide the development of RAG systems across various scenarios and data types, XRAG conducts performance evaluations of its orchestrators.

Figure 1: Schematic overview of the XRAG framework. Icon “” indicates that this is an agent-based method..
Unified Benchmark Datasets: Dual Assessment of Retrieval and Generation. To enhance the uniformity of datasets in RAG research, XRAG compiles and formats four prevalent benchmark datasets, preprocessing them into a unified format. This standardization enables concurrent assessment of both retrieval and generation, streamlining comparative evaluations across RAG modules and orchestrators.
Comprehensive Testing Methodologies: Multidimensional Evaluation Framework. To overcome the absence of a holistic evaluation system for RAG components, XRAG introduces an evaluation benchmark encompassing three perspectives thorough evaluation of retrieval and generation. . It comprises Conventional Retrieval Evaluation for retrieval-unit matching, Conventional Generation Evaluation for generation tests based on generative-token matching, and Cognitive LLM Evaluation for generation tests based on semantic understanding.
In data management, benchmarks ensure fair performance evaluation by providing detailed insights beyond end-to-end metrics into components like query optimizers and retrieval models in RAG systems. While RAG systems are often viewed through the lens of natural language processing, their effectiveness is fundamentally governed by the quality, organization, and accessibility of the underlying knowledge corpus—a classic data management concern [19]. Existing methods in database systems for AI, such as SAGE [20], ARAG [21], and scRAG [22], often lack standardized datasets and metrics to specifically diagnose the retrieval component. Our work bridges this gap by introducing a benchmark framework that applies data management’s rigorous evaluation principles to the RAG pipeline, enabling a systematic assessment of how data curation, indexing, and retrieval strategies ultimately impact the quality of generated answers. In certain database systems, such as HTAP databases [23], [24] and DB-GPT [25], XRAG can handle unstructured data and leverage RAG technology for retrieval and evaluation, enabling these database systems to be applied to scenarios such as generation and inference.
Retrieval-Augmented Generation [1]–[8] has been widely adopted as an effective technique for mitigating hallucination issues in large language models across various complex generation and reasoning tasks. These tasks typically require retrieving critical information from large-scale databases to ensure accurate outcomes and logically sound reasoning processes. Toolkits like LangChain [12] and LlamaIndex [13], modularize the RAG process, increasing adaptability and broadening its applications. FastRAG [14] and RALLE [15] allow users to assemble RAG systems with core components, fostering more flexible implementations. AutoRAG [17] further supports users by identifying optimal RAG pipelines for custom data, facilitating bespoke RAG systems. LocalRQA [16] and RAGLAB [11] focus on RAG training, offering scripts for various component training. FlashRAG [18] and RAGLAB [11] advance algorithmic reproducibility in RAG systems by integrating numerous algorithms into a unified framework, supporting efficient replication of existing methods and promoting innovation in algorithm development. Despite their restricted scalability, undeveloped evaluation protocols, absent agentic RAG analysis, and non-standardized metrics, modular RAG frameworks pervade current engineering practice. Meanwhile, researchers are progressively modularizing RAG workflows to address the dataset retrieval requirements in large language model generation tasks. Inspired by these modular RAG frameworks, we introduce XRAG to evaluate foundational components of advanced RAG modules comprehensively.
Fig. 1 delineates the integrated modules and schematic structure of the XRAG framework. The framework is stratified into datasets and corpus, advanced components, orchestrator, and evaluators, integrated through XRAG’s board and config hook 2. The overall structure progresses from foundational to application-oriented components. Designed with a modular architecture, XRAG enables users to accomplish: preparation of normalized RAG datasets (Section 3.3), assembly of the RAG components (Section 3.1), orchestration of the RAG workflow (Section 3.2) and evaluation of the RAG system’s core components (Section 3.4).

Figure 3: Schematic of the Orchestrator’s Logic in Coordinating Agentic RAG System Components..
\({\clubsuit}\) Pre-retrieval Before retrieval, the pre-retrieval components leverage LLMs to refine user queries, enhancing the quality and relevance of the information retrieval process. Key
methodologies include Step-back Prompting (SBPT [26]): Broaden’s queries to enrich contextual grounding for answers, enhancing the
contextual foundation for answer generation. Hypothetical Document Embedding (HyDE [27]): Transmutes the original query into a form that
better aligns with the indexed documents, improving retrieval alignment and efficacy.
\({\spadesuit}\) Retriever We use two basic retrieval models as benchmarks: BGE-Large and JINA-Large, along with their open-source and consistently embedding models. For advanced retrieval strategies, we
integrate the LlamaIndex to facilitate standard advanced methods. Reciprocal Rerank Fusion Retriever (RRFusion [28]) fuses indexes with
a BM25-based retriever, capturing both semantic relations and keyword relevance. Both retrievers assign scores, enabling reciprocal reranking for node sorting without additional models or excessive computation. For dense retrieval, SentenceWindow Retriever
(StParser) parses documents into single sentences per node, incorporating surrounding sentences for added context.
\({\blacktriangledown}\) Post-processor To improve retrieval accuracy and efficiency, XRAG uses post-processors like rerankers to refine nodes before returning them. We integrate the BGE reranker (BGE-RRK), which computes similarity scores using a Cross-Encoder model. Additionally, JINA-Reranker-V2 (JINA-RRK) supports high-accuracy multilingual document reranking.
\({\blacktriangle}\) Generator The XRAG framework integrates various LLM generators, including those from HuggingFace Transformers APIs 3, ensuring compatibility with open-source LLMs. It also integrates the Ollama 4 framework, supporting the localized use of LLMs. In addition to open-source models, the generator module of XRAG includes support for closed-source LLM APIs. Thus, users can access diverse capabilities while retaining the option to use proprietary models.
With the advancement of RAG technology, modern agentic RAG frameworks are no longer confined to a linear pipeline structure. Instead, they employ more sophisticated orchestration methods to arrange fundamental RAG components, enhancing performance and adapting to diverse application scenarios. We use orchestrator modules to organize and manage the execution logic and workflow of RAG components. As illustrated in Fig. 3, the XRAG framework includes five types of orchestrators: sequential, conditional, iterative, parallel, and hybrid.
\({\clubsuit}\) Sequential The sequential orchestrator operates through the sequential orchestration of advanced components to perform retrieval, and is suited for simple application scenarios. Extending beyond Naive RAG, XRAG’s sequential orchestrator leverages advanced modules to optimize retrieval performance while managing computational costs. With this orchestrator, the XRAG framework’s workflow strictly follows a linear sequence of steps—“pre-retrieval→retrieval→post-processing→generation”—executed step-by-step to retrieve contents and generate answers.
\({\spadesuit}\) Conditional In the XRAG framework, we employ a conditional orchestrator to implement RAG methods that require conditional branching. This orchestrator selects the retrieval method according to the type of query, and dynamically adjusts the execution sequence and logic of RAG components based on specific conditions or rules. We have integrated Self-RAG [29] as a typical application of the conditional orchestrator, which employs self-reflection to determine whether retrieval is necessary. Additionally, Open-RAG [30], which performs targeted retrieval by first classifying queries, can also serve as an example of this conditional orchestration approach.
\({♥}\)Iterative The XRAG framework supports the use of an iterative orchestrator to implement RAG methods requiring multiple iterations. This orchestrator enables RAG components to execute repeatedly across rounds, progressively refining retrieval results and generated content until the criteria are met. As an advanced iterative orchestrator, SIM-RAG [31], which is capable of performing multiple retrieval steps and refining prompts during the iterative process, has been integrated into the XRAG framework. We have incorporated RFM-RAG [32] as another implementation of the iterative orchestrator. RFM-RAG dynamically constructs an evidence pool through iterative retrieval and formulates targeted queries until termination.
\({\blacktriangledown}\) Parallel To enable RAG methods requiring parallel logic, the XRAG framework supports the use of a parallel orchestrator. This orchestrator allows multiple RAG components to
operate in logical parallelism, as opposed to the conditional orchestrator that relies on selection logic. As a classic parallel-orchestrated RAG technique, the retrieval logic of Reciprocal Rerank Fusion Retriever (RRFusion [28]) has been integrated into the XRAG framework as an orchestrator. Both retrievers in RRFusion assign scores in parallel, enabling reciprocal reranking
for node sorting without additional models or excessive computation. The SeaKR [33] method, which performs parallel retrievals with multiple groups
and selects the optimal retrieval for generation, has also been integrated into the XRAG framework.
\({\blacktriangle}\) Hybrid The XRAG framework supports the use of a hybrid orchestrator to address complex RAG scenarios where a single orchestrator proves insufficient. The hybrid orchestrator can combine multiple orchestration logics to accommodate sophisticated RAG requirements. The framework integrates the Adapt-RAG [34] method as an instance of this hybrid orchestrator. Adapt-RAG incorporates both conditional and iterative orchestration logic, dynamically switching between direct and iterative retrieval depending on the complexity of the query, to achieve a flexible and efficient retrieval process.
| Size | Corpus | Multi-hop | Constrained | Numerical | Set-logical | ||||
| Train | Validation | Test | Documents | Source | |||||
| HotpotQA (HQA) | 86,830 | 8,680 | 968 | 508,826 | Wikipedia | ||||
| DropQA (DQA) | 78,241 | 7,824 | 870 | 6,147 | Wikipedia | ||||
| NaturalQA (NQA) | 100,093 | 10,010 | 1,112 | 49,815 | Wikipedia | ||||
| 43,658 | 50 | 100 | 37,885 | SEC Filings | |||||
We collect and preprocess four benchmark datasets for the XRAG framework, emphasising rigorous experimental validation of RAG systems. We develop a unified dataset structured to facilitate performance testing for both retrieval and generation modules, incorporating standardized formats:
User-Query||Retrieval-Context||Retrieval-Context.IDS||Golden-Context||Golden-Context.IDS||Actual-Response||Expected-Answer.
XRAG provides a unified architecture for retrieval and question-answering datasets 5, specifically HoppotQA [35], DropQA [36], NaturalQA [37] and FinanceBench [8]. The corpus used for indexing is derived from the metadata of these datasets’ training, validation, and test sets. This methodology aligns with previous works [38] and supports the efficient deployment of vector databases. Table 2 shows that the HotpotQA corpus contains the highest document count, followed by NaturalQA, indicating that retrieval difficulty escalates with the number of documents required per query. []{#changemark:FedE4FIN Dataset label=“changemark:FedE4FIN Dataset”} The FinanceBench [8], [39] dataset consists of 37,885 financial documents covering 40 companies that are publicly traded in the USA.
Moreover, these datasets address complex RAG question-answering scenarios, including Multi-hop Queries, Constrained Queries, Numerical Reasoning, and Logical Reasoning tasks. Multi-hop questions depend on iteratively retrieved documents and their interrelations to deduce the answer. Constrained Q&A generates each answer alongside a corresponding constraint or condition rather than providing a standalone response. Numerical reasoning involves performing arithmetic operations such as addition, subtraction, sorting, and counting. Set-logical reasoning addresses complex logical problems involving relationships among retrieved chunks.
We constructed retrievable documents using metadata from the original datasets, standardizing retrieval objects as document IDs for testing. Retrieval is successful if the retrieved chunk node corresponds to the annotated document ID. This method ensures consistency in retrieval labels and eliminates discrepancies caused by varying document chunking strategies. For the test set, we limit the number of samples to mitigate the high token cost associated with RAG and LLM evaluations. In HQA, NQA, and DQA, instead of evaluating the entire test set, we apply a sampling-based averaging method, reducing token usage while preserving reliability. For FQA, which has a smaller test set, we use all test data for evaluation.
The respective prompts of XRAG for the HQA, DQA, NQA and FQA datasets are listed below.
Context information is below.
\(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\)
Given the context information and no prior knowledge, answer the question:
{query_str}
We have the opportunity to refine the original answer.
(only if needed) with some more context below.
\(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\)
Given the new context, refine the original answer to better.
Answer the question: query_str
If the context isn’t proper, output the original answer again.
Original Answer: existing_answer
Context information is below.
\(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\)
Given the context information and no prior knowledge. Please provide a brief, shortest possible answer, ideally just one word for the following question:
Question: who has sold more records Oasis or Coldplay?
Expected Answer: Oasis
We have the opportunity to refine the original answer.
(only if needed) with some more context below.
\(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\) \(\cdots\)
Given the new context, refine the original answer to better.
Answer the question: query_str
If the context isn’t proper, output the original answer again.
Original Answer: existing_answer
To assess the quality of the RAG components, we integrate the Jury [40], a comprehensive package for the evaluation of NLG systems, with RAG community evaluation tools such as UpTrain6 and DeepEval7. XRAG evaluators are pivotal in determining the effectiveness of both the retrieval and generation components. They are categorized into three groups: Conventional Retrieval Evaluation, Conventional Generation Evaluation, and Cognitive LLM Evaluation.
Conventional Retrieval Evaluation (ConR Evaluator). It supports six primary metrics: F1, Mean Reciprocal Rank (MRR), and Mean Average Precision (MAP), along with Hit@1 and Hit@10. Additionally, it includes the DCG family of metrics,
which assesses the effectiveness of ranking models by evaluating the quality of ordered results (retrieval-context.ids). This family comprises Discounted Cumulative Gain (DCG), Normalized Discounted Cumulative Gain (NDCG), and Ideal Discounted
Cumulative Gain (IDCG). IDCG is the maximum DCG that can be obtained if the results are ideally ranked – arranged in descending order of their relevance (golden-context.ids).
Conventional Generation Evaluation (ConG Evaluator). These generative-token matching metrics can be classified into three broad categories. N-gram similarity metrics: ChrF [41], ChrF++ [42], METEOR [43], ROUGE F1 [44] (R1, R2, RL) focus on overlap in n-grams between generation
(actual-response) and reference (expected-answer). Divergence-based metrics: MAUVE [45], Perplexity [46] measure content quality, diversity, and model learning by comparing the distribution between the generation and reference.
Error-based accuracy metrics: Word Error Rate (WER) [47], Character Error Rate (CER) [47], assess the accuracy of actual-response by calculating the differences or errors when compared with the expected-answer.
None
Figure 4: Interpretation of Cognitive LLM Evaluation Metrics.
| Retrieval Model | Generative Model | Classifier | Critic | Fusion | Adapter | |
| BGE-Large | BGE-Large-en-v1.5 | deepseek-r1-distill-llama-70b | ||||
| Self-RAG | BGE-Large-en-v1.5 | deepseek-r1-distill-llama-70b | SelfRAG-Llama2-7B | |||
| SIM-RAG | BGE-Large-en-v1.5 | deepseek-r1-distill-llama-70b | SIM-RAG-Llama3-2B | |||
| RRFusion | BGE-Large-en-v1.5 | deepseek-r1-distill-llama-70b | RRFusion [28] | |||
| Adapt-RAG | BGE-Large-en-v1.5 | deepseek-r1-distill-llama-70b | T5-Large [48] |
2.4mm
| Conventional Retrieval Evaluation (ConR Evaluator) | |||||||||
| F1 | MRR | Hit@1 | Hit@10 | MAP | NDCG | DCG\(^{\circ}\) | IDCG\(^{\circ}\) | ||
| JINA-Large | 49.80 | 64.23 | 21.42 | 94.44 | 55.17 | 70.44 | 0.9823 | 1.1795 | |
| BGE-Large | 60.66 | 72.84 | 18.29 | 97.71 | 64.13 | 78.64 | 1.1644 | 1.3656 | |
| JINA-Large | 20.88 | 24.42 | 06.90 | 34.47 | 24.42 | 26.76 | 0.3835 | 0.4482 | |
| BGE-Large | 22.58 | 27.10 | 07.12 | 42.30 | 27.10 | 29.58 | 0.4160 | 0.4849 | |
| JINA-Large | 49.20 | 62.44 | 30.31 | 88.49 | 62.44 | 66.98 | 0.8843 | 1.0120 | |
| BGE-Large | 49.90 | 63.82 | 25.68 | 93.24 | 63.82 | 69.12 | 0.8799 | 1.0300 | |
| JINA-Large | 9.65 | 40.75 | 38.00 | 43.00 | 40.75 | 41.39 | 0.5076 | 0.5268 | |
| BGE-Large | 6.05 | 26.83 | 23.00 | 29.00 | 26.83 | 27.45 | 0.3104 | 0.3278 | |
Cognitive LLM Evaluation (CogL Evaluator). It is classified into three categories: Retrieval-oriented, Generation-oriented, and Combined Retrieval & Generation. Cognitive LLM Evaluation metrics, derived from UpTrain(prefixed with ‘Up’) and DeepEval(prefixed with ‘Dp’), are classified based on the parameters unified by our XRAG framework. Response-oriented metrics involve response-related parameters including Response Relevance (Dp-ARel), Response Completeness (Up-RCmp) from DeepEval, Response Conciseness (Up-RCnc), Response Relevance (Up-RRel), and Response Validity (Up-RVal) and Response Matching (Up-RMch) from Uptrain. Retrieval-oriented metrics that lack response-related parameters and include retrieval-related parameters, assess context quality and consist of Context Relevance (Up-CRel) and Context Conciseness (Up-CCns), which come from UpTrain. Combined metrics evaluate the impact of retrieval on final responses and include Context Precision (Dp-CPre), Context Recall (Dp-CRec), Context Relevance (Dp-CRel), Response Consistency (Up-RCns), Context Utilization (Up-CUti), and Factual Accuracy (Up-FAcc), Faithfulness (Dp-Faith), and Hallucination (Dp-Hall). Detailed usage patterns of the CogL evaluation are illustrated in Fig. 4. Conventional rule-based metrics like Exact Match (EM) and ROUGE concentrate on n-gram matching, which sometimes falls short in capturing the comprehensive accuracy of language expressions; however, they remain fitting for tasks that necessitate distinct and singular responses. In contrast, metrics based on Cognitive LLMs evaluate the quality of generative language, which is particularly beneficial when the complexity of evaluative comprehension surpasses the capabilities of rule-based metrics.
XRAG evaluators have obvious advantages:
Evaluating with Multiple RAG Metrics in One Go: The XRAG evaluator allows users to simultaneously assess various RAG-specific metrics. This capability streamlines the evaluation process, enabling comprehensive performance analysis without sequential evaluations.
Standardizes the Structure of Evaluation Metrics: A unified data format simplifies the comparison between different RAG components in both retrieval and generation.
Character and Semantic \(\times\) Retrieval and Generation: It encompasses a 4-fold cross-dimensional analysis, including character-level matching tests and semantic-level understanding tests for both retrieval and generation.
|l|l|ccc|@c@|cccccccc| & & &
& & & & & & & & & & & &
& SBPT & & & & & & & & & & & &
& HyDE & & & & & & & & & & & &
& RRFusion & & & & & & & & & & & &
& StParser & & & & & & & & & & & &
& BGE-RRK & & & & & & & & & & & &
& JINA-RRK & & & & & & & & & & & &
& SBPT & & & & & & & & & & & &
& HyDE & & & & & & & & & & & &
& RRFusion & & & & & & & & & & & &
& StParser & & & & & & & & & & & &
& BGE-RRK & & & & & & & & & & & &
& JINA-RRK & & & & & & & & & & & &
& SBPT & & & & & & & & & & & &
& HyDE & & & & & & & & & & & &
& RRFusion & & & & & & & & & & & &
& StParser & & & & & & & & & & & &
& BGE-RRK & & & & & & & & & & & &
& JINA-RRK & & & & & & & & & & & &
& SBPT & & & & & & & & & & & &
& HyDE & & & & & & & & & & & &
& RRFusion & & & & & & & & & & & &
& StParser & & & & & & & & & & & &
& BGE-RRK & & & & & & & & & & & &
& JINA-RRK & & & & & & & & & & & &
| Conventional Generation Evaluation (ConG Evaluator) | ||||||||||
| Oracle: Golden-Context | ChrF | ChrF++ | METEOR | R1 | R2 | RL | PPL\(^{\circ}_{\downarrow}\) | CER\(^{\circ}_{\downarrow}\) | WER\(^{\circ}_{\downarrow}\) | |
| GPT-4o mini | 21.75\(_{ \pm $.024$}\) | 20.01\(_{ \pm $.012$}\) | 21.62\(_{ \pm $.008$}\) | 12.93\(_{ \pm $.007$}\) | 05.32\(_{ \pm $.003$}\) | 12.71\(_{ \pm $.005$}\) | 111.98\(_{ \pm $1.368$}\) | 11.08\(_{ \pm $.019$}\) | 09.75\(_{ \pm $.002$}\) | |
| llama3.1-8B | 21.08\(_{ \pm $.018$}\) | 19.30\(_{ \pm $.014$}\) | 16.71\(_{ \pm $.012$}\) | 15.98\(_{ \pm $.010$}\) | 06.40\(_{ \pm $.006$}\) | 15.89\(_{ \pm $.008$}\) | 150.34\(_{ \pm $1.600$}\) | 14.92\(_{ \pm $.017$}\) | 12.15\(_{ \pm $.009$}\) | |
| DeepSeek R1-7B | 11.66\(_{ \pm $.020$}\) | 10.37\(_{ \pm $.015$}\) | 09.53\(_{ \pm $.013$}\) | 05.10\(_{ \pm $.011$}\) | 01.75\(_{ \pm $.007$}\) | 05.01\(_{ \pm $.009$}\) | 69.22\(_{ \pm $1.450$}\) | 23.39\(_{ \pm $.021$}\) | 18.12\(_{ \pm $.008$}\) | |
| DeepSeek R1-70B | 41.23\(_{ \pm $.025$}\) | 40.06\(_{ \pm $.021$}\) | 45.26\(_{ \pm $.018$}\) | 32.22\(_{ \pm $.017$}\) | 21.09\(_{ \pm $.015$}\) | 32.00\(_{ \pm $.015$}\) | 115.31\(_{ \pm $1.950$}\) | 13.00\(_{ \pm $.014$}\) | 09.80\(_{ \pm $.006$}\) | |
| GPT-4o mini | 08.18\(_{ \pm $.018$}\) | 07.47\(_{ \pm $.017$}\) | 06.87\(_{ \pm $.012$}\) | 04.12\(_{ \pm $.010$}\) | 01.80\(_{ \pm $.006$}\) | 04.12\(_{ \pm $.008$}\) | 91.97\(_{ \pm $1.400$}\) | 44.35\(_{ \pm $.017$}\) | 14.50\(_{ \pm $.009$}\) | |
| Llama3.1-8B | 04.93\(_{ \pm $.020$}\) | 04.29\(_{ \pm $.015$}\) | 04.53\(_{ \pm $.009$}\) | 02.17\(_{ \pm $.011$}\) | 00.64\(_{ \pm $.007$}\) | 02.16\(_{ \pm $.009$}\) | 153.56\(_{ \pm $1.712$}\) | 76.50\(_{ \pm $.021$}\) | 23.63\(_{ \pm $.011$}\) | |
| DeepSeek R1-7B | 04.89\(_{ \pm $.019$}\) | 04.33\(_{ \pm $.016$}\) | 04.26\(_{ \pm $.012$}\) | 01.87\(_{ \pm $.010$}\) | 00.72\(_{ \pm $.006$}\) | 01.86\(_{ \pm $.008$}\) | 49.51\(_{ \pm $1.350$}\) | 90.94\(_{ \pm $.020$}\) | 28.58\(_{ \pm $.007$}\) | |
| DeepSeek R1-70B | 17.08\(_{ \pm $.012$}\) | 18.40\(_{ \pm $.015$}\) | 26.18\(_{ \pm $.016$}\) | 14.36\(_{ \pm $.013$}\) | 04.80\(_{ \pm $.014$}\) | 14.28\(_{ \pm $.017$}\) | 61.36\(_{ \pm $1.552$}\) | 63.34\(_{ \pm $.013$}\) | 19.43\(_{ \pm $.005$}\) | |
| GPT-4o mini | 25.34\(_{ \pm $.022$}\) | 23.98\(_{ \pm $.013$}\) | 25.89\(_{ \pm $.009$}\) | 16.20\(_{ \pm $.008$}\) | 06.95\(_{ \pm $.005$}\) | 15.52\(_{ \pm $.007$}\) | 48.50\(_{ \pm $1.239$}\) | 09.41\(_{ \pm $.020$}\) | 08.83\(_{ \pm $.006$}\) | |
| Llama3.1-8B | 22.34\(_{ \pm $.021$}\) | 20.78\(_{ \pm $.016$}\) | 18.00\(_{ \pm $.014$}\) | 17.47\(_{ \pm $.012$}\) | 07.68\(_{ \pm $.010$}\) | 16.92\(_{ \pm $.009$}\) | 124.79\(_{ \pm $1.807$}\) | 14.19\(_{ \pm $.018$}\) | 11.10\(_{ \pm $.013$}\) | |
| DeepSeek R1-7B | 11.13\(_{ \pm $.020$}\) | 09.82\(_{ \pm $.015$}\) | 08.10\(_{ \pm $.013$}\) | 04.90\(_{ \pm $.011$}\) | 01.40\(_{ \pm $.007$}\) | 04.53\(_{ \pm $.009$}\) | 40.97\(_{ \pm $1.331$}\) | 20.71\(_{ \pm $.021$}\) | 16.93\(_{ \pm $.008$}\) | |
| DeepSeek R1-70B | 28.71\(_{ \pm $.017$}\) | 27.72\(_{ \pm $.012$}\) | 33.64\(_{ \pm $.016$}\) | 18.82\(_{ \pm $.018$}\) | 10.31\(_{ \pm $.010$}\) | 18.24\(_{ \pm $.014$}\) | 46.66\(_{ \pm $1.564$}\) | 14.79\(_{ \pm $.019$}\) | 13.06\(_{ \pm $.007$}\) | |
| GPT-4o mini | 22.68\(_{ \pm $.018$}\) | 21.42\(_{ \pm $.017$}\) | 26.78\(_{ \pm $.019$}\) | 18.03\(_{ \pm $.012$}\) | 08.83\(_{ \pm $.005$}\) | 14.54\(_{ \pm $.009$}\) | 25.99\(_{ \pm $1.279$}\) | 74.47\(_{ \pm $.970$}\) | 49.81\(_{ \pm $.482$}\) | |
| Llama3.1-8B | 19.87\(_{ \pm $.017$}\) | 18.79\(_{ \pm $.016$}\) | 23.61\(_{ \pm $.010$}\) | 14.11\(_{ \pm $.011$}\) | 07.14\(_{ \pm $.006$}\) | 11.39\(_{ \pm $.009$}\) | 18.23\(_{ \pm $1.017$}\) | 57.31\(_{ \pm $.538$}\) | 46.67\(_{ \pm $.412$}\) | |
| DeepSeek R1-7B | 21.88\(_{ \pm $.015$}\) | 20.54\(_{ \pm $.014$}\) | 25.04\(_{ \pm $.016$}\) | 25.04\(_{ \pm $.019$}\) | 07.40\(_{ \pm $.006$}\) | 13.56\(_{ \pm $.010$}\) | 33.90\(_{ \pm $1.170$}\) | 37.66\(_{ \pm $.329$}\) | 30.79\(_{ \pm $.272$}\) | |
| DeepSeek R1-70B | 23.34\(_{ \pm $.016$}\) | 22.13\(_{ \pm $.015$}\) | 29.10\(_{ \pm $.018$}\) | 18.29\(_{ \pm $.012$}\) | 08.97\(_{ \pm $.004$}\) | 15.12\(_{ \pm $.005$}\) | 25.22\(_{ \pm $1.064$}\) | 39.88\(_{ \pm $.314$}\) | 30.78\(_{ \pm $.371$}\) | |
| Conventional Generation Evaluation (ConG Evaluator) | ||||||||||
| Retriever: JINA-Large | ChrF | ChrF++ | METEOR | R1 | R2 | RL | PPL\(^{\circ}_{\downarrow}\) | CER\(^{\circ}_{\downarrow}\) | WER\(^{\circ}_{\downarrow}\) | |
| GPT-4o mini | 26.65\(_{ \pm $.030$}\) | 25.20\(_{ \pm $.025$}\) | 29.81\(_{ \pm $.020$}\) | 16.87\(_{ \pm $.015$}\) | 08.82\(_{ \pm $.010$}\) | 16.72\(_{ \pm $.005$}\) | 95.72\(_{ \pm $1.245$}\) | 14.51\(_{ \pm $.025$}\) | 11.32\(_{ \pm $.010$}\) | |
| Llama3.1-8B | 37.33\(_{ \pm $.010$}\) | 35.05\(_{ \pm $.018$}\) | 32.51\(_{ \pm $.022$}\) | 34.80\(_{ \pm $.013$}\) | 18.77\(_{ \pm $.012$}\) | 34.58\(_{ \pm $.007$}\) | 173.88\(_{ \pm $1.209$}\) | 09.50\(_{ \pm $.018$}\) | 07.83\(_{ \pm $.012$}\) | |
| DeepSeek R1-7B | 19.28\(_{ \pm $.022$}\) | 18.18\(_{ \pm $.018$}\) | 22.62\(_{ \pm $.012$}\) | 10.90\(_{ \pm $.008$}\) | 04.97\(_{ \pm $.004$}\) | 11.04\(_{ \pm $.009$}\) | 77.40\(_{ \pm $1.235$}\) | 20.45\(_{ \pm $.020$}\) | 15.70\(_{ \pm $.015$}\) | |
| DeepSeek R1-70B | 23.81\(_{ \pm $.025$}\) | 22.55\(_{ \pm $.016$}\) | 27.99\(_{ \pm $.018$}\) | 15.32\(_{ \pm $.010$}\) | 08.10\(_{ \pm $.006$}\) | 15.17\(_{ \pm $.011$}\) | 78.09\(_{ \pm $1.325$}\) | 19.12\(_{ \pm $.011$}\) | 15.00\(_{ \pm $.013$}\) | |
| GPT-4o mini | 08.80\(_{ \pm $.023$}\) | 08.36\(_{ \pm $.018$}\) | 09.66\(_{ \pm $.012$}\) | 04.80\(_{ \pm $.008$}\) | 02.00\(_{ \pm $.001$}\) | 04.80\(_{ \pm $.006$}\) | 55.93\(_{ \pm $1.280$}\) | 75.33\(_{ \pm $.033$}\) | 26.38\(_{ \pm $.027$}\) | |
| Llama3.1-8B | 10.98\(_{ \pm $.028$}\) | 10.32\(_{ \pm $.022$}\) | 10.65\(_{ \pm $.017$}\) | 07.66\(_{ \pm $.012$}\) | 02.79\(_{ \pm $.006$}\) | 07.66\(_{ \pm $.009$}\) | 164.35\(_{ \pm $1.152$}\) | 73.46\(_{ \pm $.031$}\) | 27.64\(_{ \pm $.021$}\) | |
| DeepSeek R1-7B | 07.17\(_{ \pm $.029$}\) | 06.92\(_{ \pm $.018$}\) | 08.44\(_{ \pm $.013$}\) | 03.78\(_{ \pm $.007$}\) | 01.16\(_{ \pm $.005$}\) | 03.77\(_{ \pm $.008$}\) | 60.70\(_{ \pm $1.236$}\) | 69.78\(_{ \pm $.028$}\) | 23.20\(_{ \pm $.025$}\) | |
| DeepSeek R1-70B | 07.75\(_{ \pm $.026$}\) | 07.82\(_{ \pm $.017$}\) | 09.52\(_{ \pm $.019$}\) | 04.66\(_{ \pm $.014$}\) | 01.48\(_{ \pm $.008$}\) | 04.64\(_{ \pm $.012$}\) | 07.82\(_{ \pm $1.115$}\) | 73.87\(_{ \pm $.033$}\) | 23.65\(_{ \pm $.014$}\) | |
| GPT-4o mini | 29.37\(_{ \pm $.024$}\) | 28.29\(_{ \pm $.022$}\) | 32.61\(_{ \pm $.018$}\) | 19.49\(_{ \pm $.014$}\) | 11.12\(_{ \pm $.009$}\) | 19.90\(_{ \pm $.007$}\) | 53.16\(_{ \pm $1.145$}\) | 10.98\(_{ \pm $.025$}\) | 09.56\(_{ \pm $.015$}\) | |
| Llama3.1-8B | 37.43\(_{ \pm $.020$}\) | 35.65\(_{ \pm $.028$}\) | 33.30\(_{ \pm $.022$}\) | 35.24\(_{ \pm $.017$}\) | 21.57\(_{ \pm $.014$}\) | 34.74\(_{ \pm $.009$}\) | 170.36\(_{ \pm $1.851$}\) | 10.82\(_{ \pm $.018$}\) | 08.82\(_{ \pm $.014$}\) | |
| DeepSeek R1-7B | 21.16\(_{ \pm $.015$}\) | 20.10\(_{ \pm $.020$}\) | 22.50\(_{ \pm $.016$}\) | 12.93\(_{ \pm $.009$}\) | 06.29\(_{ \pm $.004$}\) | 12.43\(_{ \pm $.008$}\) | 46.83\(_{ \pm $1.136$}\) | 17.16\(_{ \pm $.025$}\) | 14.48\(_{ \pm $.015$}\) | |
| DeepSeek R1-70B | 24.20\(_{ \pm $.023$}\) | 23.17\(_{ \pm $.015$}\) | 27.39\(_{ \pm $.010$}\) | 15.57\(_{ \pm $.010$}\) | 08.08\(_{ \pm $.013$}\) | 14.99\(_{ \pm $.009$}\) | 44.19\(_{ \pm $1.104$}\) | 16.93\(_{ \pm $.009$}\) | 14.29\(_{ \pm $.012$}\) | |
| GPT-4o mini | 21.87\(_{ \pm $.020$}\) | 20.51\(_{ \pm $.017$}\) | 21.52\(_{ \pm $.019$}\) | 17.38\(_{ \pm $.020$}\) | 08.05\(_{ \pm $.011$}\) | 13.94\(_{ \pm $.014$}\) | 41.23\(_{ \pm $1.242$}\) | 51.44\(_{ \pm $.052$}\) | 39.16\(_{ \pm $.040$}\) | |
| Llama3.1-8B | 17.33\(_{ \pm $.017$}\) | 16.22\(_{ \pm $.018$}\) | 16.25\(_{ \pm $.017$}\) | 14.16\(_{ \pm $.016$}\) | 06.69\(_{ \pm $.008$}\) | 11.74\(_{ \pm $.010$}\) | 39.35\(_{ \pm $1.325$}\) | 73.47\(_{ \pm $.072$}\) | 56.16\(_{ \pm $.056$}\) | |
| DeepSeek R1-7B | 18.88\(_{ \pm $.017$}\) | 17.61\(_{ \pm $.019$}\) | 17.86\(_{ \pm $.018$}\) | 14.33\(_{ \pm $.012$}\) | 06.03\(_{ \pm $.008$}\) | 11.39\(_{ \pm $.010$}\) | 34.59\(_{ \pm $1.211$}\) | 36.77\(_{ \pm $.032$}\) | 28.14\(_{ \pm $.030$}\) | |
| DeepSeek R1-70B | 21.06\(_{ \pm $.023$}\) | 19.63\(_{ \pm $.015$}\) | 20.90\(_{ \pm $.010$}\) | 16.36\(_{ \pm $.010$}\) | 07.21\(_{ \pm $.013$}\) | 12.71\(_{ \pm $.009$}\) | 34.42\(_{ \pm $1.104$}\) | 29.01\(_{ \pm $.009$}\) | 23.04\(_{ \pm $.012$}\) | |
| Conventional Generation Evaluation (ConG Evaluator) | ||||||||||
| Retriever: BGE-Large | ChrF | ChrF++ | METEOR | R1 | R2 | RL | PPL\(^{\circ}_{\downarrow}\) | CER\(^{\circ}_{\downarrow}\) | WER\(^{\circ}_{\downarrow}\) | |
| GPT-4o mini | 28.23\(_{ \pm .030}\) | 26.85\(_{ \pm .025}\) | 33.07\(_{ \pm .020}\) | 17.96\(_{ \pm .015}\) | 09.51\(_{ \pm .010}\) | 17.86\(_{ \pm .005}\) | 90.51\(_{ \pm 1.145}\) | 13.60\(_{ \pm .025}\) | 11.02\(_{ \pm .010}\) | |
| Llama3.1-8B | 40.63\(_{ \pm .010}\) | 38.34\(_{ \pm .018}\) | 36.24\(_{ \pm .022}\) | 36.33\(_{ \pm .013}\) | 21.31\(_{ \pm .012}\) | 36.33\(_{ \pm .007}\) | 181.71\(_{ \pm 1.155}\) | 10.40\(_{ \pm .007}\) | 08.10\(_{ \pm .012}\) | |
| DeepSeek R1-7B | 20.02\(_{ \pm .022}\) | 18.76\(_{ \pm .018}\) | 23.71\(_{ \pm .012}\) | 11.40\(_{ \pm .008}\) | 05.19\(_{ \pm .004}\) | 11.33\(_{ \pm .009}\) | 81.34\(_{ \pm 1.235}\) | 21.46\(_{ \pm .025}\) | 16.47\(_{ \pm .015}\) | |
| DeepSeek R1-70B | 26.06\(_{ \pm $.023$}\) | 24.78\(_{ \pm $.012$}\) | 31.08\(_{ \pm $.015$}\) | 17.22\(_{ \pm $.010$}\) | 08.95\(_{ \pm $.017$}\) | 17.17\(_{ \pm $.010$}\) | 79.91\(_{ \pm $1.260$}\) | 18.39\(_{ \pm $.008$}\) | 14.26\(_{ \pm $.011$}\) | |
| GPT-4o mini | 08.89\(_{ \pm .025}\) | 08.48\(_{ \pm .018}\) | 10.38\(_{ \pm .012}\) | 05.04\(_{ \pm .008}\) | 02.11\(_{ \pm .004}\) | 05.03\(_{ \pm .006}\) | 48.22\(_{ \pm 1.228}\) | 76.53\(_{ \pm .035}\) | 27.95\(_{ \pm .025}\) | |
| Llama3.1-8B | 10.85\(_{ \pm .028}\) | 10.27\(_{ \pm .022}\) | 11.59\(_{ \pm .017}\) | 07.58\(_{ \pm .012}\) | 03.08\(_{ \pm .006}\) | 07.53\(_{ \pm .009}\) | 148.43\(_{ \pm 1.072}\) | 78.57\(_{ \pm .019}\) | 30.62\(_{ \pm .026}\) | |
| DeepSeek R1-7B | 07.49\(_{ \pm .029}\) | 07.20\(_{ \pm .018}\) | 08.63\(_{ \pm .013}\) | 03.18\(_{ \pm .007}\) | 00.93\(_{ \pm .005}\) | 03.16\(_{ \pm .008}\) | 56.18\(_{ \pm 1.091}\) | 63.03\(_{ \pm .028}\) | 23.02\(_{ \pm .010}\) | |
| DeepSeek R1-70B | 08.67\(_{ \pm $.021$}\) | 08.66\(_{ \pm $.014$}\) | 10.58\(_{ \pm $.017$}\) | 04.99\(_{ \pm $.013$}\) | 01.62\(_{ \pm $.016$}\) | 04.98\(_{ \pm $.017$}\) | 65.68\(_{ \pm $1.118$}\) | 61.99\(_{ \pm $.003$}\) | 20.22\(_{ \pm $.012$}\) | |
| GPT-4o mini | 29.37\(_{ \pm .024}\) | 28.29\(_{ \pm .022}\) | 32.61\(_{ \pm .018}\) | 19.49\(_{ \pm .014}\) | 11.12\(_{ \pm .009}\) | 18.99\(_{ \pm .007}\) | 53.16\(_{ \pm 1.222}\) | 10.98\(_{ \pm .025}\) | 09.56\(_{ \pm .004}\) | |
| Llama3.1-8B | 37.28\(_{ \pm .020}\) | 35.50\(_{ \pm .028}\) | 32.73\(_{ \pm .022}\) | 34.72\(_{ \pm .017}\) | 20.88\(_{ \pm .014}\) | 34.15\(_{ \pm .009}\) | 158.86\(_{ \pm 1.450}\) | 10.60\(_{ \pm .018}\) | 08.84\(_{ \pm .014}\) | |
| DeepSeek R1-7B | 23.51\(_{ \pm .015}\) | 22.50\(_{ \pm .020}\) | 26.39\(_{ \pm .016}\) | 14.48\(_{ \pm .009}\) | 07.64\(_{ \pm .004}\) | 14.18\(_{ \pm .008}\) | 50.35\(_{ \pm 1.230}\) | 17.33\(_{ \pm .025}\) | 14.15\(_{ \pm .009}\) | |
| DeepSeek R1-70B | 25.52\(_{ \pm $.023$}\) | 24.47\(_{ \pm $.018$}\) | 29.35\(_{ \pm $.019$}\) | 16.41\(_{ \pm $.017$}\) | 08.27\(_{ \pm $.016$}\) | 15.78\(_{ \pm $.010$}\) | 45.49\(_{ \pm $1.114$}\) | 16.07\(_{ \pm $.007$}\) | 13.75\(_{ \pm $.013$}\) | |
| GPT-4o mini | 20.47\(_{ \pm .019}\) | 19.19\(_{ \pm .017}\) | 19.18\(_{ \pm .020}\) | 15.87\(_{ \pm .015}\) | 06.72\(_{ \pm .011}\) | 12.37\(_{ \pm .013}\) | 19.19\(_{ \pm 0.839}\) | 38.12\(_{ \pm .023}\) | 28.36\(_{ \pm .021}\) | |
| Llama3.1-8B | 15.55\(_{ \pm .020}\) | 14.51\(_{ \pm .028}\) | 14.89\(_{ \pm .022}\) | 12.11\(_{ \pm .017}\) | 04.74\(_{ \pm .014}\) | 09.22\(_{ \pm .009}\) | 30.67\(_{ \pm 1.450}\) | 49.94\(_{ \pm .018}\) | 42.36\(_{ \pm .014}\) | |
| DeepSeek R1-7B | 19.04\(_{ \pm .015}\) | 17.67\(_{ \pm .020}\) | 16.48\(_{ \pm .016}\) | 13.44\(_{ \pm .009}\) | 05.52\(_{ \pm .004}\) | 10.88\(_{ \pm .008}\) | 38.17\(_{ \pm 1.230}\) | 29.81\(_{ \pm .025}\) | 22.31\(_{ \pm .009}\) | |
| DeepSeek R1-70B | 19.82\(_{ \pm $.015$}\) | 18.47\(_{ \pm $.016$}\) | 19.14\(_{ \pm $.012$}\) | 14.04\(_{ \pm $.012$}\) | 05.91\(_{ \pm $.007$}\) | 11.20\(_{ \pm $.010$}\) | 32.78\(_{ \pm $1.467$}\) | 26.33\(_{ \pm $.018$}\) | 20.20\(_{ \pm $.016$}\) | |
| CogL [Retrieval] | CogL [Generation] | ||||||||
| Retriever: BGE-Large | Up-CRel | Up-CCns | Dp-ARel | Dp-RCmp | Dp-RCnc | Dp-RRel | Dp-RVal | Dp-RMch | |
| GPT-3.5 Turbo | 0.7352\(_{ \pm 0.012}\) | 0.9201\(_{ \pm 0.023}\) | 0.9367\(_{ \pm 0.034}\) | 0.7667\(_{ \pm 0.045}\) | 0.9358\(_{ \pm 0.056}\) | 0.7856\(_{ \pm 0.067}\) | 0.9733\(_{ \pm 0.078}\) | 0.1854\(_{ \pm 0.089}\) | |
| 84.33\(_{ \pm 1.234}\) | 89.67\(_{ \pm 2.345}\) | 98.72\(_{ \pm 1.456}\) | 98.72\(_{ \pm 1.456}\) | 98.67\(_{ \pm 1.678}\) | 99.00\(_{ \pm 1.789}\) | 98.33\(_{ \pm 1.890}\) | 98.67\(_{ \pm 1.678}\) | ||
| GPT-3.5 Turbo | 0.6856\(_{ \pm 0.121}\) | 0.3604\(_{ \pm 0.142}\) | 0.9900\(_{ \pm 0.263}\) | 0.8417\(_{ \pm 0.084}\) | 0.9609\(_{ \pm 0.105}\) | 0.8441\(_{ \pm 0.226}\) | 0.9867\(_{ \pm 0.147}\) | 0.2060\(_{ \pm 0.068}\) | |
| 97.00\(_{ \pm 1.176}\) | 94.33\(_{ \pm 1.115}\) | 99.00\(_{ \pm 1.303}\) | 93.31\(_{ \pm 2.004}\) | 98.00\(_{ \pm 1.223}\) | 98.33\(_{ \pm 1.606}\) | 98.33\(_{ \pm 1.200}\) | 89.33\(_{ \pm 1.001}\) | ||
| GPT-3.5 Turbo | 0.8878\(_{ \pm 0.031}\) | 0.4133\(_{ \pm 0.052}\) | 0.9100\(_{ \pm 0.073}\) | 0.8061\(_{ \pm 0.094}\) | 0.8827\(_{ \pm 0.015}\) | 0.8214\(_{ \pm 0.036}\) | 0.9763\(_{ \pm 0.057}\) | 0.4574\(_{ \pm 0.078}\) | |
| 98.67\(_{ \pm 1.678}\) | 94.33\(_{ \pm 1.115}\) | 98.56\(_{ \pm 1.121}\) | 98.33\(_{ \pm 1.200}\) | 98.00\(_{ \pm 1.505}\) | 98.33\(_{ \pm 1.200}\) | 98.33\(_{ \pm 1.200}\) | 94.33\(_{ \pm 1.115}\) | ||
| CogL [Combined Retrieval & Generation] | |||||||||
| Retriever: BGE-Large | Dp-CPre | Dp-CRec | Dp-CRel | Up-RCns | Up-CUti | Up-FAcc | Dp-Fath | Dp-Hall | |
| GPT-3.5 Turbo | 0.9457\(_{ \pm 0.022}\) | 0.6455\(_{ \pm 0.034}\) | 0.6812\(_{ \pm 0.046}\) | 0.8318\(_{ \pm 0.058}\) | 0.6870\(_{ \pm 0.070}\) | 0.7516\(_{ \pm 0.082}\) | 0.9197\(_{ \pm 0.094}\) | 0.5537\(_{ \pm 0.106}\) | |
| 92.00\(_{ \pm 1.345}\) | 99.67\(_{ \pm 1.678}\) | 99.33\(_{ \pm 1.456}\) | 99.67\(_{ \pm 1.678}\) | 92.67\(_{ \pm 1.789}\) | 92.00\(_{ \pm 1.901}\) | 99.67\(_{ \pm 1.678}\) | 99.33\(_{ \pm 1.456}\) | ||
| GPT-3.5 Turbo | 0.8691\(_{ \pm 0.112}\) | 0.6254\(_{ \pm 0.134}\) | 0.8333\(_{ \pm 0.156}\) | 0.7450\(_{ \pm 0.178}\) | 0.6702\(_{ \pm 0.190}\) | 0.5326\(_{ \pm 0.202}\) | 0.7637\(_{ \pm 0.214}\) | 0.7333\(_{ \pm 0.226}\) | |
| 99.33\(_{ \pm 1.456}\) | 97.00\(_{ \pm 3.567}\) | 99.67\(_{ \pm 1.678}\) | 99.67\(_{ \pm 1.678}\) | 95.67\(_{ \pm 1.901}\) | 98.33\(_{ \pm 2.012}\) | 97.00\(_{ \pm 2.123}\) | 95.27\(_{ \pm 2.012}\) | ||
| GPT-3.5 Turbo | 0.9742\(_{ \pm 0.033}\) | 0.8769\(_{ \pm 0.045}\) | 0.9384\(_{ \pm 0.057}\) | 0.8948\(_{ \pm 0.069}\) | 0.6888\(_{ \pm 0.081}\) | 0.8485\(_{ \pm 0.093}\) | 0.9070\(_{ \pm 0.105}\) | 0.3417\(_{ \pm 0.117}\) | |
| 99.33\(_{ \pm 1.456}\) | 99.33\(_{ \pm 1.345}\) | 99.33\(_{ \pm 1.456}\) | 98.67\(_{ \pm 1.567}\) | 98.67\(_{ \pm 1.678}\) | 97.33\(_{ \pm 1.789}\) | 86.33\(_{ \pm 1.901}\) | 95.27\(_{ \pm 2.012}\) | ||
| Orchestrator | Conventional Generation Evaluation (ConG Evaluator) | ||||||||||
| ChrF | ChrF++ | METEOR | R1 | R2 | RL | PPL\(^{\circ}_{\downarrow}\) | CER\(^{\circ}_{\downarrow}\) | WER\(^{\circ}_{\downarrow}\) | |||
| BGE-Large | Sequential | 26.06\(_{ \pm $.023$}\) | 24.78\(_{ \pm $.012$}\) | 31.08\(_{ \pm $.015$}\) | 17.22\(_{ \pm $.010$}\) | 08.95\(_{ \pm $.017$}\) | 17.17\(_{ \pm $.010$}\) | 79.91\(_{ \pm $1.260$}\) | 18.39\(_{ \pm $.008$}\) | 14.26\(_{ \pm $.011$}\) | |
| Self-RAG | Conditional | 17.26\(_{ \pm $.016$}\) | 15.72\(_{ \pm $.013$}\) | 13.00\(_{ \pm $.016$}\) | 11.78\(_{ \pm $.012$}\) | 05.50\(_{ \pm $.011$}\) | 11.72\(_{ \pm $.012$}\) | 134.21\(_{ \pm $1.853$}\) | 10.38\(_{ \pm $.012$}\) | 08.55\(_{ \pm $.011$}\) | |
| SIM-RAG | Iterative | 62.30\(_{ \pm $.018$}\) | 60.58\(_{ \pm $.019$}\) | 52.39\(_{ \pm $.020$}\) | 65.64\(_{ \pm $.015$}\) | 39.83\(_{ \pm $.017$}\) | 65.48\(_{ \pm $.009$}\) | 267.62\(_{ \pm $1.857$}\) | 72.89\(_{ \pm $.015$}\) | 74.62\(_{ \pm $.009$}\) | |
| RRFusion | Parallel | 23.14\(_{ \pm $.013$}\) | 21.08\(_{ \pm $.012$}\) | 25.47\(_{ \pm $.015$}\) | 13.46\(_{ \pm $.017$}\) | 13.45\(_{ \pm $.019$}\) | 24.59\(_{ \pm $.014$}\) | 99.87\(_{ \pm $1.516$}\) | 18.39\(_{ \pm $.009$}\) | 14.26\(_{ \pm $.017$}\) | |
| Adapt-RAG | Hybrid | 31.20\(_{ \pm $.018$}\) | 29.91\(_{ \pm $.012$}\) | 33.56\(_{ \pm $.016$}\) | 23.43\(_{ \pm $.018$}\) | 14.10\(_{ \pm $.016$}\) | 23.17\(_{ \pm $.012$}\) | 106.73\(_{ \pm $1.683$}\) | 19.16\(_{ \pm $.019$}\) | 14.13\(_{ \pm $.019$}\) | |
| BGE-Large | Sequential | 19.82\(_{ \pm $.016$}\) | 18.47\(_{ \pm $.013$}\) | 19.14\(_{ \pm $.014$}\) | 14.04\(_{ \pm $.009$}\) | 05.91\(_{ \pm $.008$}\) | 11.20\(_{ \pm $.007$}\) | 32.78\(_{ \pm $0.614$}\) | 26.33\(_{ \pm $.018$}\) | 20.20\(_{ \pm $.015$}\) | |
| Self-RAG | Conditional | 11.98\(_{ \pm $.011$}\) | 10.53\(_{ \pm $.008$}\) | 07.87\(_{ \pm $.011$}\) | 07.13\(_{ \pm $.005$}\) | 02.38\(_{ \pm $.005$}\) | 06.09\(_{ \pm $.012$}\) | 192.74\(_{ \pm $1.476$}\) | 05.40\(_{ \pm $.011$}\) | 04.69\(_{ \pm $.011$}\) | |
| SIM-RAG | Iterative | 21.12\(_{ \pm $.015$}\) | 20.19\(_{ \pm $.015$}\) | 15.81\(_{ \pm $.017$}\) | 23.05\(_{ \pm $.013$}\) | 09.73\(_{ \pm $.014$}\) | 21.92\(_{ \pm $.007$}\) | 242.16\(_{ \pm $2.008$}\) | 00.95\(_{ \pm $.003$}\) | 01.10\(_{ \pm $.004$}\) | |
| RRFusion | Parallel | 18.83\(_{ \pm $.015$}\) | 17.31\(_{ \pm $.013$}\) | 15.67\(_{ \pm $.011$}\) | 13.60\(_{ \pm $.012$}\) | 05.21\(_{ \pm $.007$}\) | 10.91\(_{ \pm $.010$}\) | 38.83\(_{ \pm $0.536$}\) | 35.38\(_{ \pm $.020$}\) | 26.84\(_{ \pm $.017$}\) | |
| Adapt-RAG | Hybrid | 19.97\(_{ \pm $.014$}\) | 18.43\(_{ \pm $.013$}\) | 18.07\(_{ \pm $.011$}\) | 14.57\(_{ \pm $.012$}\) | 05.86\(_{ \pm $.008$}\) | 12.16\(_{ \pm $.009$}\) | 54.08\(_{ \pm $0.733$}\) | 19.83\(_{ \pm $.016$}\) | 15.21\(_{ \pm $.014$}\) | |
For document preprocessing, we used SentenceSplitter(chunk size: 128 tokens, overlap: 20 tokens) to segment documents into chunks and build a vector index. We adhered to LlamaIndex configurations for other RAG components, including the refine module for response synthesis. To ensure compatibility and efficiency, XRAG integrates Huggingface Transformers. All Q&A LLMs were set with Temperature \(=0\) to ensure experimental consistency 8. Consequently, the evaluation metrics measure retrieval accuracy based on 3 retrieval nodes, fully encompassing the assumptions of most datasets that typically consider only one or two golden contextual nodes. The generator model’s context window—encompassing the query, prompt, retrieved context, and response content—is configured to 4096 tokens. To ensure a fair comparison when testing the orchestrators, we used identical modules where feasible, as detailed in Table 3. Due to the high cost associated with token processing during LLM (OpenAI) reasoning and evaluation, Cognitive LLM Evaluation (CogL) metrics were included as a pilot study to demonstrate the XRAG framework’s capability in semantic assessment.
[]{#changemark:standard deviations label=“changemark:standard deviations”} Experiments involving LLM generation were repeated three times, and standard deviations are reported in the tables of generation results.
Computational Resource Due to inherent design and size constraints, the deployment environments for each model are distinct. For the DQA dataset, testing was conducted on a single NVIDIA V100 GPU (32GB); the indexing phase (single-threaded) and the search-and-generation phase (four-threaded) required approximately one and two hours, respectively, with the BGE-Large index occupying 496 MB and the JINA-Large index occupying 391 MB of disk space. Similarly, on the NQA dataset using the same V100 hardware, the indexing and search phases took three and four hours, with index sizes of 5.4 GB for BGE-Large and 4.2 GB for JINA-Large. For the HQA dataset, an NVIDIA L20 GPU (48GB) was employed; both indexing and search processes were executed in a single-threaded manner, lasting four and eight hours, while the BGE-Large and JINA-Large indices utilized 18 GB and 14 GB of storage, respectively. Finally, the FQA dataset was evaluated on an NVIDIA RTX 4090 GPU (24GB), both single-threaded indexing and search/generation were completed in one hour each, with the BGE-Large and JINA-Large indices requiring 8.8 GB and 6.9 GB of disk space.
The retrieval performance varies sensibly across the four datasets, with the poorest quality observed on DQA and FQA in Table 4. Since DQA requires advanced discrete reasoning [50] and FQA demands paragraph understanding of financial documents, it presents a greater retrieval challenge.
i. Different datasets should focus on different testing metrics. The NDCG metric reflects that the basic retrieval model performs reasonably well in relevance and ranking accuracy on HotpotQA and NaturalQA datasets. Ignoring ranking accuracy, a high Hit@10 score (>0.8) indicates a substantial likelihood of retrieving semantically relevant document blocks. The Hit@1 metric measures the ability to return the correct answer as the top-ranked result, making it suitable for tasks with a single retrieval target (e.g., the golden single passage in the NaturalQA dataset). However, it is less effective for scenarios requiring multiple equally prioritized context targets, as seen in the HotpotQA dataset. Overall, the retrieval system performs well on HotpotQA and NaturalQA but faces challenges on DropQA, due to the complexity of the answer (Low Hit@1 scores reflect difficulty in retrieving the most relevant results.).
ii. To improve retrieval performance, priority should be given to retrieval and post-retrieval. Compared to the basic retriever in Table 4 and the advanced retriever in Table ¿tbl:advanced95conr95retrieval?, the highlighted results indicate that adopting advanced retrieval modules, which integrate additional matching information, can enhance retrieval effectiveness. For example, RRFusion combines dense vectors with keyword retrieval, and the sentence window includes the context of chunk nodes in the retrieval objects. Specifically, it is observed that reranking methods can markedly improve performance, particularly for challenging retrieval tasks such as DQA and FQA. For instance, both BGE-RRK and JINA-RRK outperform the basic retriever. This is because the reranker can evaluate the relevance of retrieved data, prioritizing content most likely to provide accurate and relevant answers. By allowing the LLM to focus on these top-ranked contexts during answer generation, it significantly enhances the accuracy and quality of responses.












Figure 5: Comparison of retrieval and generation effects as query length varies. Experiments conducted on the HQA dataset (Test)..
In examining the question-and-answer (Q&A) component, it is essential to collectively consider Tables 5, 6, 7 and 10. Table 5 provides the test results when the human-annotated retrieval output is directly entered into the large model for Q&A purposes. Table 6 and Table 7 illustrate the outcomes when the retriever employs the JINA-Large and BGE-Large models, respectively, to identify relevant sentences for the large model. Tables 8 and 9 present the results of a Cognitive LLM evaluation conducted on the output generated by the XRAG system utilizing the BGE-Large retriever.
In Table 8, the Dp-RMch metric scores below 0.5, while all other metrics exceed 0.8. This suggests that Dp-RMch is unsuitable for most non-critical scenarios, as it may misclassify responses that are semantically correct. The probability score \({P}_{sc}\) in Table 8 and Table 9 indicates that LLM testing depends on API requests, which may incur packet loss due to unstable requests, long processing times, timeout limits, or server-side errors. This reflects a particular weakness of LLM testing, even though the average request success rate reaches over 85%.
i. When the model parameter size is relatively small, directly supplying the large model with golden context may not yield optimal results for these datasets. Our analysis reveals that the experimental outcomes in Tables 6, and 7 generally surpass those in Table 5, with the exception of the results obtained using the DeepSeek-R1-70B model. The golden context typically comprises a single text passage (DQA and NQA) or two passages (HQA), which may provide inadequate information for the large model. Additionally, due to the limited reasoning capacity of small-scale LLMs, they may encounter difficulties in analyzing results from such concise texts, particularly for questions necessitating numerical computations and logical reasoning. Our retrieval model delivers the top k (top 3) results to the LLM, filtering and ranking context information to provide more comprehensive data. Some retrieved data, though not labeled as “golden context” for not being direct answers, are highly relevant to the query and contribute positively to the reasoning process. This observation implies that for any retrieval-augmented generation task, evaluating only the retrieval results may not accurately represent the overall RAG performance; concurrent evaluation of both retrieval and large model Q&A generation is imperative.
ii. Choosing the right type of LLM for a RAG task could be superior to merely increasing the model’s parameters. When comparing with various LLMs, it was observed that the DeepSeek R1-7B and the Deepseek R1-70B inference model exhibited the poor performance. The high hallucination rate of the DeepSeek model series [51] is fundamentally at odds with the stringent accuracy demands of RAG scenarios. At Wikipedia datasets, the most consistent performance was observed with the Llama3.1-8B model, which achieved optimal Q&A results when combined with either JINA-Large or BGE-Large retrieval outputs. Nonetheless, the perplexity (PPL) value of DeepSeek R1-7B and Deepseek R1-70B was the lowest. It is important to note that PPL and Q&A metrics assess different facets of the model: PPL emphasizes text fluency and generality, whereas ChrF and METEOR focus on the precise alignment between generated text and expected answers. While the DeepSeek series of models may not be closely aligned with expected answers in specific tasks, yet their strengths lie in superior semantic coherence and text fluency.
As shown in Table 10, RAG methods employing advanced orchestrators demonstrate substantial improvements in generation quality. In agentic RAG methodologies, SIM-RAG and Adapt-RAG demonstrate superior performance, whereas Self-RAG underperforms compared to the BGE retrieval results. RRFusion, as a traditional parallel retrieval method, exhibits a performance gap when compared to agentic RAG approaches such as Adapt-RAG and SIM-RAG.
i. Multi-hop question answering is more suitable for iterative orchestrators. In Table 10, SIM-RAG substantially outperforms other methods on the HQA dataset, which contains a high volume of multi-hop queries. For multi-hop question-answering tasks, an iterative orchestrator can progressively retrieve information from each hop of the multi-hop data through their cyclical process of optimizing retrieval results and generated content, until the retrieved content is sufficient to answer the question or no more information can be obtained.
ii. Conditional orchestrators often rely on heuristic decision logic, resulting in relatively poor transferability. In Table 10, Self-RAG demonstrates underwhelming performance, which stems from the heuristic-based classifier within its conditional orchestrator. The classifier in conditional orchestrator often requires specific adjustments based on data characteristics and application scenarios, and fails to deliver effective classification when handling more complex datasets.
| Latency(s) | Token(k) | |||||
| Index | Pre-retrieval | Retrieval | Post-processor | Generation | ||
| BGE-Large | 2087 | 1641 | 296 | 161 | ||
| JINA-Large | 2105 | 1459 | 256 | 165 | ||
| SBPT | 2087 | 183 | 1489 | 301 | 232 | |
| HyDE | 2087 | 492 | 1410 | 288 | 441 | |
| RRFusion | 2087 | 7119 | 256 | 98 | ||
| StParser | 2087 | 1921 | 159 | 63 | ||
| BGE-RRK | 2087 | 1836 | 1232 | 235 | 163 | |
| JINA-RRK | 2087 | 2106 | 1387 | 253 | 165 | |
| Latency(s) | Token(k) | |||||
| Index | Critic | Classifier | Retrieval | Generation | ||
| Adapt-RAG | 2087 | 1215 | 1215 | 1215 | 3118 | 179 |
| SIM-RAG | 2087 | 59 | 4085 | 5346 | 871 | |
| Self-RAG | 2087 | 42 | 1881 | 225 | 98 | |
As shown in Table 11, taking the vanilla RAG methods (e.g., BGE-Large and JINA-Large) as a reference, pre-retrieval methods such as SBPT (71k) and HyDE (280k) introduce only a slight increase of LLM token usage. While advanced retrieval methods (e.g., RRFusion and StParser) come at the cost of considerably greater retrieval latency (7119s for RRFusion, 1921s for StParser), they compensate by consuming fewer LLM tokens, thanks to heuristic optimizations applied during retrieval. Post-processors add some latency during the reranking stage. Orchestrators typically involve complex retrieval logic, including multiple retrieval steps and multiple rounds of LLM interactions, resulting in higher latency and greater token consumption. Considering the performance (as shown in Table 10 and Table ¿tbl:advanced95conr95retrieval?) of retrieval modules alongside their latency and LLM token costs (as shown in Table 11), The rerank method is highly recommendable, as it consistently demonstrates stable performance gains across all datasets (e.g., Hit@1: +73.9% for BGE-RRK vs. BGE-Large on FQA) without incurring substantial increases in latency (+11.8% for BGE-RRK vs. BGE-Large) or token consumption (+1.2% for BGE-RRK vs. BGE-Large). In latency-insensitive scenarios, employing an orchestrator is also a favorable option, where a more sophisticated retrieval workflow can trade computational resources for enhanced retrieval and generation performance.
Q1: Whether longer queries have a greater impact? The illustration (as shown in Fig. 5) indicates a positive correlation between query length and the performance of several metrics, notably Hit@1 and METEOR, which demonstrate an ascending trajectory with increased query length. This correlation implies that the utilization of longer queries may augment the efficacy of retrieval and query-answering systems. Such enhancements are likely due to the enriched information that longer queries provide, facilitating a more precise interpretation of queries.
Q2:Whether more context has a greater impact? The illustration depicted in Fig. 6 demonstrates that the performance of query-answering systems remains relatively stable as the number of retrieval contexts increases. This observation suggests that augmenting the quantity of retrieval contexts may not significantly enhance model performance. Upon analyzing the mean value ranges, it is evident that for instance, in the ROUGE-1 metric, the mean value only moderately increases from 0.31 to 0.41 with the augmentation of retrieval contexts. This modest variation implies that the impact of increasing the number of contexts on performance improvement is limited. Furthermore, the observation of maximum values reaching 1.0 in multiple figures indicates that the key to enhancing performance may lie in improving the precision of retrieval. This involves identifying a few contexts most relevant to the query, rather than merely increasing the number of retrieved contexts. The ChrF++ and METEOR metrics exhibit relatively stable performance across varying numbers of retrieval contexts. This suggests that these metrics are not particularly sensitive to variations in the number of contexts. Consequently, this underscores the importance of focusing on enhancing the relevance and precision of retrieval results in the optimization of the retrieval module within RAG systems, rather than increasing the quantity of retrieved contexts.
Q3: Whether problem hard induce challenges in both retrieval and generation processes? As shown in Tables 12 and 13, consistent with expectations, both retrieval and generative models achieve higher scores on easy datasets compared to harder datasets. From an evaluation perspective, more stringent metrics—such as F1 and Hit@1 for retrieval, and ChrF and METEOR for generation—are notably sensitive to dataset difficulty (e.g., On the Hit@1 metric, BGE-Large scores 97.00 on the easy dataset but only 70.00 on the hard one, a decline of approximately 28%). This sensitivity occurs because stricter metrics are more effective at detecting performance declines, which are inherent as question difficulty increases.
| MAP | |||||||||||||
| CER\(^{\circ}_{\downarrow}\) | |||||||||||||
Q4: Whether superior retrieval results ensures superior generation? As shown in Figure 7,on the hard dataset, when the model hits at Hit@1, the mean of Chrf++ metric (0.28) is 0.14 higher than Chrf++ when the model non-hits (0.14). This indicates that successful retrieval substantially enhances answer quality for difficult questions. On the easy and medium datasets, the gap in answer quality between Hit@1 hits and non-hits is relatively small (0.06 for easy, 0.04 for medium). Moreover, when Hit@1 hits, there are a small number of samples with poor answer quality (chrF < 0.1), indicating that a good retrieval result does not necessarily yield a correct answer. This explains the phenomenon observed in Section 5.2: "Retrieved context outperforms golden context".
Q5: Whether more iterations of RAG orchestrators lead to better generation results? As shown in Figure 8, the number of queries requiring 5 iterations was higher on the hard dataset (52) than on the easy (34) and medium (41) datasets, indicating that more challenging subsets require greater iteration counts. When the iteration limit has not been reached (1\(\leq\) count\(\leq\)4), the quality of answer results improves markedly with increased iterations on the three subsets of HotpotQA dataset. This validates the suitability of iterative orchestration for multi-hop question answering tasks. For questions that are too difficult to answer by SIM-RAG, unsatisfactory answers may still be obtained after reaching the maximum iteration limit, which is why performance degrades significantly once the iteration count reaches 5.
This work introduces XRAG, an open-source framework for benchmarking advanced RAG systems, which enables researchers to construct RAG systems more efficiently from datasets. It facilitates the selection of appropriate retrieval modules and logic based on data characteristics, and allows for the evaluation of retrieval performance. In the future, we plan to enhance XRAG in the following aspects: i. Enable support for RAG component training to handle more complex data scenarios. ii. Integrate a wider range of benchmark datasets for evaluation, such as OpenQA [52], [53], long-form Q&A [54], [55], and multiple-choice Q&A [56], [57]. []{#changemark:robustness assessment label=“changemark:robustness assessment”} iii. Add the robustness evaluation related to dirty and malformed queries.
We encourage contributions from the open-source community to advance the XRAG framework. Our goal is to refine the XRAG framework by delivering a more efficient and dependable platform with comprehensive evaluation and development tools for RAG research community.
In the preparation of this paper, Deepseek-R1 was used exclusively for the purpose of polishing and refining the linguistic style of certain sentences to improve readability and fluency in section 1, 3, and 7. All core intellectual contributions, including but not limited to:
Original Ideas and Novel Viewpoints: Any innovative concepts, hypotheses, and critical analysis are the product of the authors’ own work.
Experimental Data and Results: All code, figures, findings, and interpretations thereof were generated, designed, collected, and analyzed by the authors.
Substantive Descriptions of the Work: The description of the methodology, experimental procedures, and discussion of the research implications were entirely authored by the research team.
Code available at: https://github.com/DocAILab/XRAG.↩︎
As shown in the Fig. 2, we have implemented the XRAG demo. These two parts are mainly functions within the demo and are not the focus of the experimental analysis.↩︎
The dataset is CC BY-NC-SA 4.0 licensed (we maintained the same license agreement as the original dataset.), accessible via the URL https://huggingface.co/datasets/DocAILab/XRAG_Dataset. We also provide a documentation for the XRAG: https://docailab.github.io/XRAG/ on how to use the data and code.↩︎
Nonetheless, using large models for generation or evaluation always results in minor variations, possibly due to randomness in MoE training or prompt interpretation biases [49].↩︎