TraceBound Diagnoses Adaptive Retrieval Failures in Knowledge-Graph QA
There's a new diagnostic tool called TraceBound that suggests adaptive retrieval might actually hurt performance when using knowledge graphs to answer questions. This research, found on arXiv (2607.24800v1), presents TraceBound as an efficient tool for ARK-style retrievers that rely on text-heavy knowledge graphs. It creates a short query profile before retrieval, offers quick hints after failures, and tracks progress while keeping the underlying graph data and metrics unchanged. In tests like STaRK and other subsets, this approach helps with analysis but tends to lower retrieval quality when using open-weight controllers. Investigating paired trajectories shows that repeated calls and ineffective exploration budgets lead to worse performance, and tighter interaction budgets cut trajectory lengths without improving outcomes.
Key facts
- TraceBound is a diagnostic protocol for adaptive retrieval in knowledge-graph QA.
- It profiles queries and issues trace hints after failure symptoms.
- Added conditioning improves inspectability but reduces retrieval quality.
- Degradation is due to repeated calls, zero-result calls, and misallocated budget.
- Stricter interaction budgets shorten trajectories without improvement.
- Study uses STaRK validation and held-out subsets.
- Open-weight controllers are used in the experiments.
- Graph data, tools, gold labels, and ranking metrics are kept fixed.
Entities
Institutions
- arXiv