# The Missing Link in AI: Graph-Native Data Modeling Why graph construction is the critical bottleneck for AI systems - **Source:** [O'Reilly Radar](https://www.oreilly.com/radar) - **Published:** 2026-09-28 - **Topic:** [Data & AI](https://brifing.si/c/data-ai) - **Original article:** - **On Brifing:** https://brifing.si/s/90b953cd-fc7e-4f69-958e-b33b432ccc20 ## Graph modeling gap Current AI discussions focus on graph neural networks and retrieval systems, skipping the crucial step of transforming raw data into meaningful graphs. Organizations have customer records, support conversations, and telemetry data scattered across formats. Converting these requires deciding entity boundaries, relationship semantics, temporal representation, and conflict resolution. These foundational choices determine all subsequent predictions and agent decisions, making graph modeling a first-class AI concern rather than just preprocessing. ## Schema limitations exposed Recent research tested whether database schemas designed for transactions work well as machine learning graphs. Across 26 relational tasks, direct schema conversions suffered from information overload and semantic fragmentation. Performance improved when researchers removed distracting connections and added meaningful dependencies missing from original schemas. This demonstrates that graph structure itself must be optimized for specific reasoning tasks, not just inherited from operational systems. ## Multiple graph views The same data can support entity-centric, event-centric, and evidence-centric graph representations. Entity graphs excel at identity resolution, event graphs capture temporal processes, while evidence graphs support provenance tracking. Microsoft's GraphRAG uses entity graphs for document retrieval, while molecular property prediction requires different node-edge semantics. The optimal view depends on whether the system prioritizes relationships, timelines, or evidence chains. ## Evaluation loop needed Effective graph construction requires testing multiple plausible structures against downstream tasks. Provenance tracking becomes critical to understand edge sources and confidence levels. Benchmarking revealed cases where GraphRAG underperformed vanilla RAG, showing that graph construction, retrieval and generation must be evaluated together. Prediction errors indicate missing relationships, while retrieval failures expose granularity issues - making the graph itself part of the learning problem. ## Five graph applications Modeled graphs support: 1) Query/analytics via path traversals and community detection, 2) Prediction using GNNs and transformers, 3) Retrieval through GraphRAG's entity indexing, 4) Agent systems needing relational memory, and 5) Foundation models requiring transferable graph semantics. Each application benefits from different graph properties - fraud detection needs precise relationships, while knowledge graphs prioritize evidence chains. ## Agent system requirements Graphs naturally represent agent memories, plans, and multi-agent relationships. Research organizes graph uses around planning (task dependencies), memory (state persistence), tool use (capability modeling), and coordination (agent relationships). The design challenge is identifying which agent components benefit from graph representation versus simpler data structures. Emerging architectures use graphs for inspectable, updatable agent state across interactions. ## Foundation model challenges Graph foundation models aim to transfer learning across domains, but face semantic variation problems. Nodes represent entirely different concepts in molecular versus transaction graphs. Current approaches combine graph backbones with self-supervised objectives and language models. The hardest part is bridging structural and semantic differences - a molecule's functional group differs fundamentally from a customer's purchase history in relationship semantics. ## Systematic modeling frontier The next breakthrough requires systems that propose, test and maintain multiple graph views from raw data. Such systems must handle entities across tables/text/events, preserve metadata like confidence scores, suggest structural alternatives, and evaluate based on downstream performance. Carefully modeled graphs can serve multiple applications without rebuilding identity and provenance layers - making graph construction a distinct engineering discipline. ## Sources covering this story - https://www.oreilly.com/radar/from-raw-data-to-graph-native-ai/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._