Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

What 180k words look like as a temporal knowledge graph (Oz series)

Details

External ID
49053986
Source
HN
Company
—
Product
What 180k words look like as a temporal knowledge graph (Oz series)
Website domain
synaptale.com
Launched
July 26, 2026
Cohort
—
Upvotes
22
Upvotes percentile
0.7353643966547192
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

The graph is free to explore and requires no registration.SynapTale builds a model of a story as a temporal graph made up of nodes (entities) and edges (their actions and relationships). The graph is not a visualization of the wiki. The wiki, timelines, relationship histories, and analytics are projections of the graph.The current demo contains 232 entities, 1,852 edges, and a snapshot of the story’s state at every chapter. By chapter 100, it still remembers a promise made in chapter 8 and turns the story into a set of source-verifiable facts.The most interesting things can be found in the graph itself and in the Analytics tab. A few things I found:1. The character with the highest kill count is the Tin Woodman—the same character who cries over a beetle he accidentally crushed. Dorothy comes second, with three killing events. 2. Dorothy never deceives anyone during the first 100 chapters of the series. 3. The Scarecrow’s debt to the stork has remained active for 92 chapters, starting in chapter 8. 4. The Cowardly Lion ranks third by number of threats. 5. The first 100 chapters contain 60 secrets and 254 dialogue events.Technical details1. Five different multi-agent pipelines combining LLMs and NLP: a prescan, ontology construction, chapter-by-chapter graph extraction, retrospective validation over spans of dozens of chapters, and a linguistic prescan for speech profiles and linguistic edges.2. A living story needs a living graph. It has to account for time, because entities and the relationships between them evolve. A simple is_active field is not enough.I ended up with three types of edges:event: an instantaneous action; identity: a fact; state: a persistent action whose termination requires justification and a supporting quote from the text.The vast majority of edges are events and end in the same chapter in which they began. This allows the system to scale well, since only a minority of state and identity edges remain continuously active.3. Ontology. You cannot simply ask an LLM to extract entities and relationships into a graph. With every chapter, even the smartest model will keep inventing unimportant fields, creating new aliases for existing fields, and representing the same fields inconsistently.Before extracting the graph, the system therefore performs an ontology scan across the entire story. It captures story-specific entity and edge types, along with their fields and descriptions.4. Epistemics. Events are only one part of a story. It is also important to understand how information is distributed, which is difficult to represent using event edges alone.I addressed this by introducing a new node type: epistemic nodes, which capture different entities’ perspectives on the same fact. Subtle hints can still be missed, the system is not yet perfect in this area.

Enrichment

Theme
ai storytelling and children's education
Vertical
Media & entertainment
Function
Analytics & BI
Audience
B2C
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
temporal knowledge graph visualization of oz series
Manually corrected
False

Could you build this?

Partial Displaying a graph and invoking LLMs is vibe-codeable, but maintaining an accurate, non-hallucinatory temporal graph across 180,000 words requires sophisticated entity resolution and state tracking.

What it would actually take: A robust system requires an automated NLP/LLM extraction pipeline with coreference resolution, entity disambiguation, and interval-based temporal logic (e.g., using Neo4j or a custom graph engine). The difficult challenge is reconciling character states, chronological paradoxes, and evolving secrets over novel-length texts without accumulating cascading extraction errors.

Discussion

11 comments analyzed.

Competitors mentioned: Codex (for story state tracking and compilation), Manual wikis (hand-compiled character/plot tracking)

Concerns raised: Scaling limits and context window growth for very long series, Need for author consent before running on published works

Feature requests: Story 'compiler' that tracks character state changes through plot events, Real-time updates as new chapters are released, Writing aid to detect contradictions and unresolved plot lines

Competitors

Other products that read as similar to this one — 45 launches clear the similarity bar, closest 8 shown.

Attention rank: #15 of 46 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 244 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a analytics & bi tool for Legal yet.