NVIDIA's Auto Ontology Stops AI Agents From Querying the Wrong Data
NVIDIA released Auto Ontology, an open-source Python framework that builds semantic graph layers over enterprise data so agents generate SQL deterministically with provenance.
- NVIDIA released Auto Ontology, an Apache-2.0 framework for building semantic graph layers over enterprise databases.
- Agents get grounded SQL with provenance, validated against certified definitions and lineage from existing metadata.
- Supports Databricks, Postgres, Snowflake, DuckDB sources via Next.js frontend, FastAPI backend, pgvector store.
- Exposes context through MCP server, CLI, and REST API for Cursor, Claude Desktop, custom agents.
- Defaults to NVIDIA NIM Nemotron models but accepts any OpenAI-compatible endpoint via environment triplets.
- Deploys via Docker Compose or Helm; benchmark harness lives in separate ontology-sql-eval repo.
NVIDIA has released Auto Ontology, an open-source Python framework designed to make LLM-generated SQL more reliable. It builds a graph-based semantic layer over enterprise databases, giving analytics agents approved definitions, relationships, and lineage instead of leaving them to infer meaning from column names.
The project uses the Apache 2.0 license and supports local and Kubernetes deployments. At the time of the source page, its GitHub repository had 207 stars.
Why valid SQL still fails
Schema retrieval can help an agent produce SQL that parses and runs, yet the result may still use the wrong revenue field, combine incompatible metrics, or ignore an organization’s reporting rules. A syntactically correct query offers little protection against semantic errors.
Auto Ontology places a semantic layer between the agent and the warehouse. This machine-readable map records where data lives, what fields and metrics mean, how they should be used, where they came from, and which concepts are related. The framework generates that layer from existing metadata, ontologies, and semantic models, then exposes it through the Model Context Protocol, a command-line interface, and a REST API.
From metadata to answer
The framework organizes its workflow into four stages:
- Discover: Generate ontologies from enterprise metadata, connect existing semantic models, and build an agent-readable knowledge graph.
- Ground: Map questions to governed metrics, entities, and relationships while reconciling inconsistent definitions across systems.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.
Comments
