Hi-Q: Hierarchical Evidence-guided
Query Refinement for
Multi-Hop Question Answering

1 Department of Computer Science and Engineering, POSTECH
2 Graduate School of Artificial Intelligence, POSTECH

Corresponding author

Overview of Hi-Q: granularity control and dependency-aware binary decomposition producing a binary decomposition tree

Hi-Q tests each query node against retrieved evidence, expands only the unresolved ones, and resolves prerequisites before dependents.

Abstract

A central bottleneck in multi-hop question answering is that the granularity at which a question is expressed often differs from the granularity at which corpus evidence is retrievable. Existing methods address this mismatch by imposing fixed graph structures over the corpus, by iteratively reformulating the query, or by executing a generated program over it — but none of them explicitly decides when a query unit is already supported by evidence and when it should be refined.

We formulate this bottleneck as retrievable granularity discovery and introduce Hi-Q, an evidence-conditioned framework for hierarchical query refinement. At each query node, a resolution operator tests whether retrieved evidence supports the current query unit. Resolved nodes terminate; unresolved nodes are expanded by a dependency-preserving binary operator and checked by a semantic coverage verifier. Hi-Q therefore grows a query tree whose topology is determined by corpus support signals rather than by a fixed decomposition template or a pre-built graph.

“When was the start of the battle of the birthplace of the performer of III?”

III → Stanton Moore → New Orleans → Battle of New Orleans → December 14, 1814

What the paper claims

Granularity is the thing to search for

Multi-hop RAG is the problem of finding the query unit at which a reasoning step becomes both retrievable and answerable under a given corpus — not the problem of producing a logically valid decomposition.

The reader's failure is the trigger

A node is expanded when the grounded reader cannot answer from what was retrieved. Nothing is trained for this; we show the choice is a cost-sensitive threshold on the probability that the node is unresolved.

What you condition on beats whether you learned it

Any policy that reads only the question carries a regret that no amount of query-only training data removes. A learned router of exactly that kind routes 959 of 1,000 questions the same way — and scores below a constant policy.

Why granularity

The facts needed for a multi-hop question sit in different documents at a fine grain, while the question arrives as a single coarse sentence. Too coarse and the retriever matches isolated terms; too fine and the query loses the constraints that made it answerable. The three failures below are all the same mismatch.

Three failure modes of multi-hop retrieval on the query about the battle of the birthplace of the performer of III
Granularity failures in multi-hop retrieval. All three methods run the same query against the same corpus.

(a) Single retrieval

Returns passages matching “III” and “battle” separately — Leopold III at Sempach, the Greek III Army Corps at Korytsa — and none of the gold passages.

(b) Graph RAG

Enters a pre-built graph at surface-matched seeds. The traversal ranks those same two wrong passages first, so the reader abstains.

(c) Iterative retrieval

Asks for the performer's birthplace first, binds “III” to Philip III of Spain, and carries Madrid through every later step to answer 1936.

Method

Hi-Q starts from the original question and attempts it at the granularity it arrives in. Only when the retrieved evidence fails to support that unit does it expand, and the expansion is ordered so that a prerequisite is resolved before whatever depends on it.

Granularity control

The resolution operator rewrites the current query from the accumulated history, retrieves the top-k passages, and has a grounded reader answer from them. If the reader answers, the node stops. If it abstains, the retrieved evidence does not jointly support this query unit and the node becomes eligible for refinement. Writing the two error costs — expanding a node that was already answerable, stopping at one that was not — turns the decision into a threshold on the probability that the node is unresolved.

Dependency-aware binary decomposition

An unresolved node is split into exactly two sub-queries: one that resolves the bridge fact, and one that uses that bridge to reach the parent's answer. Splitting in two restricts sequential depth rather than expressiveness — a plan with m leaf information needs is organized as at most m−1 binary reductions. The left branch runs first and its answer, evidence, and partial context enter the history before the right branch does, so a dependent sub-query is never retrieved against while still under-specified.

Semantic coverage verification

Before either sub-query is solved, a verifier checks that resolving them in order recovers the parent's intent without adding, omitting, or reordering constraints. One repair attempt is allowed; if the revised split is still inconsistent, the node is marked non-decomposable and that branch stops. Across datasets the verifier repairs 14.8–18.8% of triggered decompositions.

Results

Our primary setting is full-corpus retrieval, where dependent evidence must be located among open-domain distractors rather than inside a small annotated pool of supporting and distractor passages. Reader is GPT-4o-mini; retriever is NV-Embed-v2 with k = 5.

MuSiQue-full 2Wiki-full HotpotQA-full
Method EMF1EMF1EMF1
PropRAG graph25.838.652.159.3not reported
Self-Ask iterative22.228.141.746.930.037.5
Least-to-Most24.334.030.734.045.459.1
IRCoT24.434.935.038.952.063.6
Coding agent program16.829.616.534.731.147.1
RLM19.629.134.041.630.141.1
Hi-Q37.450.662.071.457.469.9
Exact Match and F1 under full-corpus retrieval. PropRAG's full-corpus results cover two of the three benchmarks. Recall@2 and Recall@5, and the restricted supporting/distractor setting, are in the paper.
52.3 EM · 64.0 F1 averaged over the three benchmarks, ahead of IRCoT by 15.1 EM / 18.2 F1
7.9 → 42.7% all-gold passage coverage, root retrieval vs. the decomposed leaves at the same budget
8.6× cheaper than IRCoT per question at a matched LLM-call budget, while more accurate

The trigger is precise without being trained

On 100 normal MuSiQue queries the false rejection rate is 11%, and every null output is attributable to missing or incomplete evidence rather than blind abstention. On 50 adversarially unanswerable queries Hi-Q identifies 49 as unanswerable, a 2% false acceptance rate. Replacing the trigger with an always-decompose policy costs 3.4 EM — which also bounds what any trigger error can cost, since always-decompose is the limiting case of over-triggering.

Ahead at every reasoning depth

Exact Match and F1 by number of reasoning hops on MuSiQue, comparing Hi-Q with IRCoT and PropRAG
Accuracy by hop count on MuSiQue. Every method degrades as more dependent steps are required, but Hi-Q stays ahead at each depth — 55.2 and 39.2 F1 at 3 and 4 hops, against 43.4 / 35.4 for IRCoT and 43.1 / 26.9 for PropRAG.

BibTeX

@article{kim2026hiq,
  title   = {Hi-Q: Hierarchical Evidence-guided Query Refinement
             for Multi-Hop Question Answering},
  author  = {Kim, Jueun and Park, Sungho and Han, Wook-Shin},
  journal = {arXiv preprint arXiv:XXXX.XXXXX},
  year    = {2026}
}