Case Studies
Jun 23, 2026
Ontology Meets Graph Databases: Multi‑Tier Visibility for Supply Chain Resilience (Real World Example #3)
NebulaGraph
In the first two articles of the Ontology series, we built the foundation. Part One introduced ontology, which has become essential in the AI era: it grounds machine intelligence in deterministic semantics, eliminates data fragmentation, and provides the shared understanding that operational AI systems require. We also showed how graph databases serve as the natural engine for making ontology practical.
Part Two moved from theory to practice. We identified the five warning signs that signal an urgent need for ontology (multi-system fragmentation, high compliance demands, long decision chains, high heterogeneity, and high inference cost) and outlined the four-stage maturity journey—from local pilot to intelligence-driven enterprise brain.
Then we turn to real‑world action. In Real World Example #1, we showed how ontology defines explicit entity types, relationships, and constraints to turn fraud detection into a relationship-intelligence problem—executed in milliseconds by NebulaGraph. In Real World Example #2, we saw how ontology types social connections (friend, coworker, shared interest) and weights them, enabling Snapchat to deliver personalized recommendations to 432 million daily users.
Now in this article, we tackle supply chain intelligence—where multi‑tier dependencies demand both semantic precision and graph‑native speed.
What This Post Covers
Why Supply Chains Demand Ontology: Traditional relational databases cannot answer multi‑tier dependency questions efficiently. Ontology defines what entities exist in the supply chain domain—suppliers, components, orders, logistics—and how they legally and operationally relate.
Case Study – ZKH: How the leading MRO (Maintenance, Repair, and Operations) platform built an ontology‑driven supply chain knowledge graph on NebulaGraph, achieving 15% gains in both precision recommendation and supply chain optimization, including a 5% improvement in order conversion rates.
Industry Extension: How ontology‑driven knowledge graphs are becoming the standard for supply chain risk management, quality tracing, and regulatory compliance across manufacturing, automotive, and life sciences.
Why Supply Chains Cannot Survive Without Ontology
Modern supply chains are not simple linear flows from supplier to manufacturer to distributor to customer. They are dense webs of dependencies spanning thousands of suppliers, sub‑suppliers, components, warehouses, logistics providers, and regulatory jurisdictions. A single part failure in tier‑3 affects production in tier‑1. A geopolitical event in one region disrupts inventory across three continents. A single component’s failure can ripple across product lines, regions, and customer segments.
Relational databases treat each relationship as a foreign key join across dozens of tables. A query tracing a component through three tiers of suppliers might require 20–30 joins, with performance degrading exponentially as path length increases. Moreover, relational schemas cannot easily encode the semantic meaning of different relationship types—SUPPLIES is legally different from SHIPS_TO, and CERTIFIED_BY carries different compliance implications than LOCATED_IN. Without ontology, these semantic distinctions are lost.
Ontology solves these problems by providing an explicit, formal specification of the supply chain domain. An ontology is your supply chain’s constitutional framework. It defines what exists in your domain and how those things can relate to each other. The ontology defines:
Entity types: Supplier, Manufacturer, Component, Product, Order, Warehouse, Customer, Logistics Provider, Jurisdiction
Relationship types: SUPPLIES, MANUFACTURES, STORES, SHIPS_TO, DEPENDS_ON, CERTIFIED_BY, LOCATED_IN
Properties: lead times, costs, risk scores, compliance status, certification expiry dates
Constraints: A supplier cannot be a sole source for a critical component without enhanced monitoring. A component flagged for quality issues triggers review of all downstream orders within a configurable time window.
With this ontology embedded in a graph database like NebulaGraph, the supply chain becomes a semantic graph. Every entity knows its type. Every relationship knows its meaning. The ontology tells the system which relationship types to follow, which constraints to apply, and which properties to evaluate; the graph database executes the traversal in milliseconds.
Case Study: ZKH – From Fragmented Data to 15% Gains in Supply Chain Performance
ZKH is an online industrial products (MRO—Maintenance, Repair, and Operations) service platform dedicated to digital transformation, serving customers across manufacturing, construction, and facility management. Before adopting NebulaGraph, ZKH faced three critical challenges typical of complex supply chains:
Data Scale and Complexity: Business expansion led to rapid growth of customer‑supplier relationships and behavioral data. Traditional databases struggled with efficient storage, querying, and real‑time analysis.
Relational Database Limitations: Significant performance bottlenecks in multi‑table joins made real‑time analysis of complex relational data impossible.
Data Value Realization Difficulty: Complex relationship data in supply chain optimization and risk warning faced challenges in data modeling, algorithm optimization, and effectiveness verification.
The Ontology‑Driven Architecture
ZKH built its ontology-driven supply chain knowledge graph on NebulaGraph using a clear semantic structure:
Data Collection: Structured data from ERP, MySQL, and SQL Server synchronizes to cloud data platforms via DataX and Flink‑CDC. Client behavior data is collected via SDK. Unstructured data (contracts, images, documents) is stored in object storage.
Data Processing: Offline computing uses MaxCompute and Spark for large‑scale batch processing; real‑time computing uses Flink for stream processing.
Data Storage: Two NebulaGraph clusters are deployed—an online service cluster for real‑time queries (customer behavior path analysis, relationship queries) and a graph algorithm cluster for complex algorithms (supplier risk assessment).
Data Services: API gateways provide unified interfaces for application access, with personalized APIs for customer behavior path analysis and supplier risk assessment.
But what makes this architecture ontology-driven is the semantic modeling embedded within it:
Explicit Entity Typing. The graph centers on products and users, with nodes typed as Supplier, Component, Customer, Order, Warehouse, and LogisticsProvider. Each node carries ontology‑defined properties unique to its type. This typing allows the system to distinguish between a “supplier” relationship (legal obligation to deliver) and a “logistics” relationship (operational delivery routing).
Typed Relationships. The ontology defines edge types such as SUPPLIES, PURCHASES, STORES, and SHIPS_TO. These types encode semantic meaning and enable the system to traverse different relationship classes with different weighting and constraint rules.
Real-time Feature Extraction. Through NebulaGraph’s GQL query language, ZKH extracts user behavioral features and supply chain dependency features in real time. These features—defined by the ontology’s property schemas—are used to optimize recommendation processes and drive supply chain personalization.
Multi‑hop Dependency Analysis. A core ontology‑driven capability is path analysis across the supply chain network. The ontology’s DEPENDS_ON relationship type, combined with SUPPLIES edges, enables the system to identify multi‑tier dependencies. When a supplier faces a disruption, the ontology defines which downstream entities are affected based on the SUPPLIES → MANUFACTURES → SHIPS_TO chain. This semantic path specification ensures that disruption impact analysis is not just fast but accurate—the system knows which relationship types to follow and which to ignore.
Measurable Results
The implementation of NebulaGraph at ZKH has achieved significant results in business scenarios such as precision recommendation and supply chain optimization. The impact is measurable:
Search recommendation click‑through rates improved by 15%.
Order conversion rates improved by 5%.
Supply chain intelligence and efficiency improvements across procurement, inventory management, and fulfillment.
Beyond these metrics, the ontology‑driven approach has enabled ZKH to uncover hidden patterns that traditional systems cannot see. Supply chain visibility now extends across previously siloed datasets—customer behavior, product inventory, supplier performance, and logistics tracking—all connected through a shared semantic framework.
From ZKH to the Industry: Why Ontology Is Becoming the Supply Chain Standard
ZKH is not alone. The wider industry is rapidly recognizing that ontology‑driven knowledge graphs are the most scalable solution for modern supply chain complexity.
Risk Monitoring. Researchers at Hitachi have developed an ontology‑guided method for supply chain risk knowledge graph extraction, leveraging large language models to extract risk knowledge from unstructured open data guided by a user‑specified ontology. The ontology actively guides the extraction process, enabling consistent and automated identification of risk knowledge across dynamic environments.
Supplier Discovery. The Open Manufacturing Capability Network (SUDOKN) project has built an ontology‑based knowledge graph representing over 1,700 manufacturers’ capabilities, using formal ontologies compliant with the Basic Formal Ontology to provide a shared knowledge backbone for supply chain analytics solutions.
Decision Support Systems. Researchers have introduced a knowledge graph‑based decision support system for resilient supply chain networks, following rigorous ontology development methodology to help supply chain risk managers make sourcing decisions.
Life Sciences. AstraZeneca has built the Operations Knowledge Fabric—a semantic, graph-powered data foundation for scalable, regulated AI—using ontologies to power an intelligent “self-healing” supply network.
The common thread across these industry applications is the same insight that drove ZKH: supply chain resilience requires multi‑tier visibility, and multi‑tier visibility requires explicit relationship semantics. Without ontology, every risk analysis is a manual exercise in stitching together fragmented data. With ontology, risk propagation becomes an automated graph query.
Conclusion: Supply Chain Resilience Requires Semantic Visibility
Across these examples, we have seen ontology at work in three demanding domains. In fraud detection, ontology turned transaction records into network intelligence. In recommendation systems, ontology turned undifferentiated connections into semantic personalization. Now in supply chain intelligence, ontology turns fragmented supplier data into multi‑tier visibility.
The message from ZKH and the broader industry is unmistakable: supply chain resilience in the AI era depends on semantic visibility. Without ontology, every disruption analysis is a manual exercise in stitching together siloed spreadsheets. With ontology embedded in a graph database like NebulaGraph, disruption impact analysis becomes an automated, semantically informed graph traversal that delivers answers in milliseconds.
If your organization manages complex supplier networks, multi‑tier dependencies, or regulatory compliance across jurisdictions, the time to adopt ontology‑driven supply chain intelligence is now.
Contact us today to learn how NebulaGraph Enterprise Edition can help you operationalize ontology across your supply chain and other critical workflows!
What’s Next: Announcing NebulaGraph v5.3
This three‑part series has focused on real‑world use cases. But we haven’t forgotten the platform that makes them possible.
We are excited to announce that the next release of NebulaGraph Enterprise Edition v5.3 will bring significant enhancements to ontology support.
The enhancements will build directly on the insights from this series: ontology is an operational necessity for enterprise AI. With NebulaGraph v5.3, operationalizing ontology across fraud detection, recommendation systems, supply chain intelligence, and beyond is more powerful and more accessible than ever.
