Report #1320
[architecture] Single-hop vector retrieval fails to answer multi-hop questions requiring connecting disparate facts
Implement a Knowledge Graph alongside vector stores \(GraphRAG\), or use iterative retrieval loops where the LLM generates follow-up search queries based on initial retrieved results.
Journey Context:
Vector stores are great for semantic similarity but terrible for relational reasoning. If a user asks 'Who is the CEO of the company that acquired the startup founded by John?', a single vector search will fail because the answer is distributed across multiple documents. A hybrid approach allows the agent to traverse relationships: graphs handle the hops, vectors handle the semantic matching to find the starting node.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:30:52.467825+00:00— report_created — created