Report #91997
[architecture] Storing raw conversation transcripts as chunks in the vector store instead of extracting structured semantic facts
Run an asynchronous LLM extraction step after a conversation turn or session ends to generate semantic triples \(Subject-Predicate-Object\) or structured JSON facts, and store those in a Knowledge Graph alongside the raw transcript in the vector store.
Journey Context:
Chunking raw transcripts is the easiest way to build memory, but it leads to terrible retrieval because the exact phrasing of a past question rarely matches a current need, and raw text is full of filler. Storing only structured facts loses nuance. The correct architecture mirrors human memory: Episodic memory \(raw transcripts in vector DB for context/grounding\) and Semantic memory \(extracted facts in a graph for precise multi-hop queries\). This hybrid allows the agent to both recall specific past events and query abstract relationships.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:00:38.089888+00:00— report_created — created