>This design relies on pretty heavy training data. How does your method work if such training data is not available, or when your data and applications do not match the statistics in your training data?
In this paper, we proposed a solution to this challenge. Specifically, we leveraged LLM critiques to generate synthetic data when suitable training data was unavailable. As demonstrated in our evaluation, this approach proved to be highly effective, outperforming silver-label methods in the case of PopQA. While testing in out-of-distribution scenarios is not the primary focus of this study, we emphasize the potential of employing LLM critiques more effectively, given their demonstrated ability to assess document relevance with notable accuracy [1]. Additionally, by collecting as much available data as possible and employing ensemble techniques, we can derive a distribution that is more generalizable across domains and datasets lacking sufficient training data.
[1] Retrieval Augmented Generation or Long-Context LLMs? A Comprehensive Study and Hybrid Approach. EMNLP 2024.
> semantic analysis on query intent and nor does any concrete semantic analysis on the text to be retrieved.
Our design intentionally avoids performing explicit semantic analysis of query intent and the text to be retrieved to prioritize simplicity and computational efficiency. We acknowledge that incorporating semantic analysis could potentially enhance the retrieval accuracy, especially in cases where query intents or ambiguous language need to be interpreted. Such analysis might better capture subtle relationships between queries and documents, leading to more precise matching. However, there are also potential drawbacks to integrating semantic analysis. It could significantly increase the system’s complexity and computational overhead, potentially impacting scalability.
In this study, we chose not to include explicit semantic analysis in our design because our primary focus was on evaluating the effectiveness of leveraging LLM critiques in achieving a balance between the efficiency of RAG inference. We aimed to establish a baseline performance that could later be extended or refined in future iterations. Nevertheless, we agree that discussing this tradeoff would provide valuable context, and we will include a discussion on the potential impact of semantic analysis and the rationale behind our design choices.
> elaborate on how the Sparse RAG approach specifically handles such time-sensitive or ambiguous queries.
Thanks for this question. Section B in the Appendix addresses the absence of sufficient context to correctly answer the question in the widely used public datasets we experimented on. For consistency with the literature, we did not modify the queries or the retrieved contexts, but we do expect that the ambiguity is impacting our results. In many cases, retrieved contexts would be assessed differently for relevance depending on the true intended meaning of the question, and different answers would be expected. It would be an interesting future exploration to augment the datasets to resolve such ambiguity, as it would likely improve the accuracy of our relevance labels and improve performance overall.
For missing time or location context, you could augment the datasets by simply adding new contexts with the missing information or appending the context to the query. For example, to handle the question "Who is the current president of the United States?", you could add a context "Today is November 18, 2024" or you could modify the query to "Who is the current president of the United States on November 18, 2024"?. In the paper, we showed that Sparse RAG performs comparably to RAG on the HotpotQA multi-hop reasoning dataset, so we expect that Sparse RAG could effectively leverage information from new contexts in the generation step, but appending such temporally specific context to the query itself would likely yield the best quality, as all contexts attend to the query.
In real world cases where the question is ambiguous, the most desirable behavior would be to request clarification before further action. In an experimental environment, we could use LLMs to rewrite the queries to contain disambiguating details without giving away the answers. Alternatively, one could simulate requesting clarification by adding an additional binary ambiguous/clear classification task for each question and augmenting the dataset with disambiguating information similar to the approach described above. Then, in evaluation, the model would classify the question's ambiguity, then request more information if necessary, then perform per-context assessment, and then perform generation.
We will add some discussion of this to the new manuscript Appendix.