The Value Network

Knowledge Graph Lakehouse: A Cloud-Native Architecture for Managing Enterprise Knowledge Graphs at Scale What if the knowledge graph were built only when a question asks for it? Enterprise knowledge graphs model connected domains well. At scale, volume, velocity and variety turn a single monolithic graph into something slow to ingest, hard to govern and often out of date. The Knowledge Graph Lakehouse inverts the order: Source documents land unchanged in a data lake A contextual index records which contexts each document is valid for (time, location, topic) Application-specific contextualized KGs are constructed on demand, only for the contexts a query names Interpretation is deferred to query time. What the system holds durably is the documents and the index. The design is grounded in KG-OLAP: contexts are cube cells, slice, dice and roll-up select and merge them, and knowledge propagates from covering contexts. Results are delivered as RDF quads, a labeled property graph or a GraphFrame. 🌍 Environmental data shows what this looks like in practice Regulated facilities change ID numbers, sit under parent corporations that acquire and spin off sites, and trade waste with sister facilities across overlapping jurisdictions. The records are spread over EPA systems such as RCRAInfo, ECHO and TRI, plus SEC filings. One lakehouse, three graphs: PFAS in a watershed: facilities, permits, pollutants, receiving waters, corporate parents Enforcement: violations, inspections, consent decrees, responsible legal entities Waste tracking: generators, transporters, manifest chains The lakehouse stays authoritative. The graph becomes a disposable perspective. 📊 Evaluation (air traffic management): Corpus grew from 28,590 to 324,456 documents; construction time for a fixed scope stayed near 2 seconds The index stayed around 1% of corpus size A new batch of 255 documents became queryable in about 18 seconds, against a 55-minute rebuild of a materialized cube Peak memory: about 1.4 GB on demand, 46 GB for the materialized build The architecture suits workloads whose scope is declared before any data is touched. Arbitrary queries over a standing graph remain better served by a materialized store. By B. Ahmad, C. G. Schuetz and L. Bozzato. Example by David G. Smith. davidgsmith.net/thoughts/why… #DataLakehouse #CloudNative #KGOLAP #DataArchitecture #ContextualKnowledgeGraphs -- 📩 The Year of the Graph Autumn 2026 newsletter issue is out! Meaning, Traversal, Reasoning, Action: The Graph Stack for Agentic AI. 👇 yearofthegraph.xyz/newslette… All things #KnowledgeGraph, #GraphDB, Graph #Analytics / #DataScience / #AI and #SemTech. Subscribe and follow to be in the know. Reach out if you’d like to be featured