We thank the reviewer for the response. We would like to expand a bit on some of the points mentioned by the reviewer.
>it is often very hard to make these assumptions for retrieval-augmented LMs at inference time due to the potential noise/irrelevance of retrieval
The assumption of "parametric is wrong but retrieved is right" does indeed define the scope of applicability of our findings. However, ensuring correct model behavior in this setting is a **necessary** step if the goal is to ensure factual correctness using RAG. Ensuring relevance and quality of the retrieved documents is another, complementary step. **Both** of these steps are necessary for the final goal of factually correct outputs.
>In addition, the analysis often focuses on the most unlikely scenarios (<5%, points 2 and 3 in the review)
We think this is an important disagreement point and would like to explain our thinking and observations. We hope this provides more insight into why we focus on the R subset.
Frequency is not the sole factor in determining the importance of a problem. For example, adversarial attacks rarely happen in practice, yet there is substantial research to ensure adversarial robustness of models. Analogously, the R subset may appear to be a "fringe case", but it is a well-defined problem for which we provide a deeper analysis.
Out of all incorrect open-book answers, the R subset contains only the ones which did not change at all after introducing the context. This specificity, together with our analysis is what makes it actionable.
Ui subset, however, includes all other incorrect answer categories "lumped" together.
If you look into the Ui subset, it is not one "prevalent scenario", but rather many of them:
We manually classify 100 samples in 𝑈𝑖 for the Mixtral on NQ:
- 42 incorrect answer format
- 10 model answer is also correct, but != GT
- 13 model answer is correct while the GT is incorrect
- 12 model being bad at reading tables
- 13 incorrect reading (prediction appears in context, but != GT)
- 4 answers not from context
- 5 model wrongly claims the answer is not in the context
- 3 context is illegible
Analysing the Ui subset, as proposed by the reviewer, would actually require separating each sub-category. This would turn each of them into actionable, but small subsets, similar to R.
>the authors acknowledge that analysis could be expanded to more prevalent scenarios
We would like to clarify that we intended to add to the revision the manual analysis above for the Ui subset, together with the provided motivation for focusing on the seemingly smaller but actionable R subset.