Report #3696
[architecture] Single vector search fails to retrieve interconnected facts needed for complex agent reasoning
Augment vector retrieval with a knowledge graph \(GraphRAG\) or iterative multi-hop retrieval. First retrieve an entity, then traverse its relationships, or prompt the LLM to generate follow-up queries based on initial retrieval results.
Journey Context:
Vector stores excel at semantic similarity but fail at relational reasoning. If an agent needs to answer 'Who is the CEO of the company that acquired the startup the user founded?', a single vector search will fail because the answer spans multiple disconnected facts. A pure graph DB fails at fuzzy semantic matching. The hybrid approach \(vector index for semantic entry points, graph edges for traversal\) solves this, trading off indexing complexity and latency for significantly higher recall on multi-hop questions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:04:03.018226+00:00— report_created — created