Nvidia – open-source auto-ontology
- ID
- 42573
- Status
- summarized
- Published
- 03 Nov 2026, 3:04 PM
- Fetched
- 04 Nov 2026, 12:27 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/NVIDIA/auto-ontology
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 04 Nov 2026, 12:28 AM
- Tags
- Audience
- developersai_agent_usersai_ml_learners
What happened
NVIDIA published Auto Ontology, an Apache-2.0 Python framework that builds a semantic, graph-based "context layer" over enterprise metadata so agents know where data lives, what a metric means, and how to query it. It generates ontologies from metadata, reconciles definitions across systems, and exposes them to agent harnesses via MCP, CLI, and API, positioning itself as complementary to semantic models teams already own. The repo shows 2.2k stars, 165 forks, 1,354 commits, and drew 223 points / 81 comments on Hacker News.
Why it matters
The README's own framing is the decision to test: an agent that answers a revenue metric faster is worthless if the number is wrong, so this is a bet on deterministic query generation over free-form text-to-SQL. Before adopting, check whether your warehouse already has dbt/semantic-layer definitions this would duplicate, and note the README excerpt gives no benchmarks, accuracy numbers, or supported-warehouse list — so the 2.2k stars reflect interest, not verified correctness. No Malaysia- or SEA-specific detail appears in the text.
Discussion angle
Has anyone actually compared ontology-backed deterministic query generation against plain text-to-SQL prompting on the same messy warehouse schema — and what broke first: definition drift, join ambiguity, or the metadata ingestion itself?