← Latest papers
💬 NLP

How Fine-Grained Should a RAG Benchmark Be? A Hierarchical Framework for Synthetic Question Generation

This paper introduces HieraRAG, a hierarchical framework and validation procedure that uses synthetic QA pairs to determine the optimal granularity for RAG benchmark dimensions by maximizing discriminative power, revealing that ideal categorization levels vary across question complexity, answer type, and linguistic variation.

Original authors: Chase M. Fensore, Kaustubh Dhole, Jason Fan, Eugene Agichtein, Joyce C. Ho

Published 2026-06-12
📖 5 min read🧠 Deep dive

Original authors: Chase M. Fensore, Kaustubh Dhole, Jason Fan, Eugene Agichtein, Joyce C. Ho

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a chef trying to figure out which recipes are the hardest for a new kitchen robot to cook. You want to test the robot, but you need to know: How detailed should your list of recipe types be?

Should you just say "Easy" and "Hard"? Or should you break it down into "Salads," "Soups," "Grilled Meats," and "Desserts"? Or maybe even further, like "Chopped Veggies," "Sliced Veggies," "Pureed Veggies," etc.?

This paper, HieraRAG, is about finding the "Goldilocks" level of detail for testing AI systems that answer questions using a library of documents (called RAG systems). The authors argue that there isn't one perfect level of detail for everything; it depends on what you are testing.

Here is the breakdown of their findings using simple analogies:

1. The Three Ingredients They Tested

The researchers looked at three different ways to describe a question, like three different ingredients in a recipe:

  • Question Complexity (QC): How much brain power does the question need? (e.g., "What is the capital of France?" vs. "Compare the economies of France and Germany.")
  • Answer Type (AT): What does the answer look like? (e.g., A single word, a list, or a long paragraph?)
  • Linguistic Variation (LV): How much does the question sound like the document it's based on? (e.g., Using the exact same words vs. using totally different words to ask the same thing.)

2. The Experiment: The "Zoom Lens"

They created nearly 6,000 fake questions and tested them on a standard AI system. They looked at these questions through three different "zoom lenses" (granularity levels):

  • Coarse (Wide Angle): Just 2 categories (e.g., Simple vs. Complex).
  • Medium (Standard Zoom): 4 categories.
  • Fine (Macro Lens): 8 very specific categories.

3. The Big Discovery: One Size Does Not Fit All

The most important finding is that different ingredients need different zoom levels.

  • Complexity (QC) needs the "Macro Lens" (Fine Detail):
    Think of this like sorting a pile of rocks. If you just say "Big" and "Small," you miss the fact that some "Small" rocks are actually jagged and dangerous, while others are smooth. The researchers found that breaking "Complexity" down into 8 tiny categories revealed the most differences in how the AI performed. The AI struggled with some specific types of complex reasoning that a simple "Hard" label would have hidden.

    • Verdict: Go Fine (8 categories).
  • Answer Type (AT) and Language (LV) need the "Standard Zoom" (Medium Detail):
    Think of this like sorting fruit. If you have "Apples" and "Oranges," that's easy. If you break "Apples" down into "Red Delicious," "Granny Smith," "Honeycrisp," "Fuji," etc., you might start getting confused because the differences between them don't actually change how the robot handles them much.
    The researchers found that once they got to 4 categories for these two types, adding more detail (going to 8) just added noise. It didn't help them understand the AI better; it just made the data messy.

    • Verdict: Stop at Medium (4 categories).

4. The "Coherence Ratio": The Quality Control Check

The authors invented a new tool called the Coherence Ratio. Imagine you are a parent dividing a large room into smaller rooms for your kids.

  • Good Coherence: You split the "Playroom" into a "Lego Corner" and a "Doll Corner." These are distinct, but they both clearly belong to "Playroom."
  • Bad Coherence: You split the "Playroom" into a "Lego Corner" and a "Kitchen Sink." The second one doesn't really fit the group; it's confusing.

The researchers used this metric to check if their 8 tiny categories were actually logical sub-groups of the 4 medium ones. They found that for "Complexity," the tiny groups were a bit messy (low coherence), but they were still useful for spotting performance differences. For "Answer Type," some of the tiny groups were very well-organized, while others were messy.

5. The "Vocabulary Gap" Surprise

They also tested what happens when the question uses words that are totally different from the document (like asking about "cars" when the document only says "automobiles").

  • The Finding: If the AI can't find the right document because the words don't match, it doesn't matter how "complex" the question is. The AI fails either way.
  • The Metaphor: It's like trying to solve a math problem when you can't find the textbook. Whether the math is "Easy" or "Hard" doesn't matter; you can't solve it without the book. The "vocabulary match" is the most important factor for finding the answer; complexity only matters after the AI has found the right page.

Summary

The paper concludes that if you want to build a good test for an AI:

  1. Don't just use "Easy" and "Hard" questions.
  2. Don't over-complicate your categories either.
  3. Tailor your test: Use very detailed categories for Complexity questions, but stick to medium-level categories for Answer Types and Language styles.

The authors provide a "recipe" (the HieraRAG framework) for other developers to figure out their own perfect level of detail, rather than just guessing.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →