Episode
Hallucinations Are a Data Architecture Problem | Sudhir Hasbe, Neo4j
- Published
- Apr 16, 2026
- Duration seconds
- 3144
- Processing state
not_requested- Canonical source
- https://share.transistor.fm/s/ec268865
Actions
POST https://stenobird.com/v1/public/podcasts/chain-of-thought-ai-agents/episodes/hallucinations-are-a-data-architecture-problem-sudhir-hasbe-neo4j/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/chain-of-thought-ai-agents/hallucinations-are-a-data-architecture-problem-sudhir-hasbe-neo4j.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Sudhir Hasbe is President and Chief Product Officer at Neo4j, the graph database company powering 84 of the Fortune 100 (Walmart, Uber, Airbus) at $200M+ ARR and a $2B+ valuation. Before Neo4j, he ran product for all of Google Cloud's data analytics services: BigQuery, Looker, Dataflow, and led the Looker acquisition. His thesis: the hallucinations we blame on AI models are really a data architecture problem. LLMs weren't trained on your enterprise knowledge, so handing them a data lake with 10,000 disconnected tables and asking them to reason is the wrong design. The fix is knowledge graphs: feeding the model a structured map of relationships, entities, and context so it can reason over meaning, not just vector similarity. Sudhir breaks down the five capabilities knowledge graphs unlock for enterprise AI: GraphRAG (moving accuracy from 60% to 97%), semantic mapping across siloed systems, context graphs, agent memory, and multi-hop reasoning. He explains three architecture patterns customers are actually shipping, why giving an LLM hundreds of tools makes it worse, and what Uber, EA Sports, Klarna, and Novo Nordisk are doing differently. This is the case for treating knowledge as infrastructure. We cover: Why enterprise AI needs a different playbook than consumer AI The five data asset types every agentic system needs: system of record, historical, memory, context, and reference How GraphRAG combines vector search and graph traversal to move from 60% accuracy to 95%+ Three architecture patterns: semantic layer only, semantic map plus domain data, full consolidation (the Klarna/Kiki model) What context graphs capture that Salesforce doesn't: the Slack and email negotiation behind every deal Why giving an LLM hundreds of tools drops accuracy, and how Uber uses knowledge…