GRAPH EXPLORER
Walk the graph, node by node
A bounded snapshot of the resolved knowledge graph — click any node to pull its live neighborhood straight from Neo4j.
INDUSTRIAL KNOWLEDGE GRAPH
Documents hold one connected truth
Worklogs, P&IDs, and inspection reports name the same asset differently. industrial brain resolves them into a single traversable graph — scroll to watch the blueprint become the graph underneath it.
Scroll
HOW RESOLUTION WORKS
One cursor movement, one connected graph.
Every frame below is rendered from the same source data flowing through industrial brain's schema-conditioned resolution pipeline.
Animated illustration showing a blueprint transforming into a connected knowledge graph as you scroll, matching the description above.
Loading 0%
Buffering…
PRODUCT SPECIFICATION
Every tier talks to the same graph.
MethodEndpointDescription
GET/healthBackend + Neo4j connectivity check
GET/entity/{value}/neighborhoodDirect connections of an entity
GET/entity/{from}/path-to/{to}Cross-document path between two entities
GET/graph/snapshotBounded graph snapshot for visualization
POST/queryNatural-language question, schema-conditioned routing
GET/demo/fallbackPre-cached proof data for offline demo mode
CAPABILITIES
Four ways into the same graph.
TRACE A PATH
Two entities, one story
The same physical asset named differently across a worklog, a P&ID, and an inspection report — resolved into a single traversable path.
ASK THE GRAPH
Plain language in, cited answer out
Questions route through schema-conditioned graph retrieval, with vector and keyword search as fallback layers.
PLANS & API
Every tier, every endpoint
Plans scale how much of the API you can call — not which features exist. Every endpoint is live in every tier's sandbox.
LIVE CONSOLE
Stop reading about it. Drive the graph.
Talks to your FastAPI backend at /health, /graph/snapshot,
/entity/… and /query. No backend running? It quietly
switches to a cached demo dataset so the prototype never dies on stage.
Loading graph…
or look up one entity — /entity/{value}/neighborhood
Enter an entity ID above, or click a node in the graph.
Trace how two entities connect across documents.
✦
Ask a plain-language question about the graph — try one of the suggestions above, or type your own.
0
Nodes per graph snapshot
0
Max hop trace depth
0
Source formats unified
0
Free neighborhood lookups
RESOLUTION PIPELINE
From raw document to queryable graph.
01
Ingest
Worklogs, P&IDs, and inspection reports are pulled in as-is, regardless of format or naming convention.
02
Extract entities
Assets, equipment, and events are identified across every document, even when named inconsistently.
03
Resolve into graph
Entities are merged into a single traversable graph in Neo4j — one connected truth per asset.
04
Query
Explore, trace a path, or ask a plain-language question — all routed through the same schema-conditioned API.
Ready to see one connected truth?
Open the graph explorer or start.