Skip to main content

Envisioning is a research institute that studies how institutions adapt to technological change.

LinkedInInstagramGitHub

Since 2010

research
  • Observatory
  • Adaptive capacity
  • Newsletter
  • Methodology
  • Origins
  • Vocab
  • RSS feeds
services
  • Signals Session
  • Bespoke Projects
  • Build Sessions
  • Pricing
  • Use cases
  • Signals
  • Signal Scan↗free
impact
  • ANBIMAFuture of Brazilian Capital Markets
  • IEEECharting the Energy Transition
  • Horizon 2045Future of Human and Planetary Security
  • WKOTechnology Scanning for Austria
solutions
  • Innovation
  • Strategy
  • Consultants
  • Foresight
  • Associations
  • Governments
  • L&D
resources
  • Partners
  • Coding for Non-Coders
  • How we work
  • Data visualization
  • Multi-Model Convergence
  • FAQ
  • Security and privacy
  • Public sector
about
  • Manifesto
  • Community
  • Events
  • Support
  • Contact
ResearchCapabilityServicesSignalsAbout
ResearchCapabilityServicesSignalsAbout
  1. Home
  2. Vocab
  3. EvoOntology

EvoOntology

A self-evolving ontology layer that data agents query at runtime through an MCP server, refined through small typed edits that are kept only when they measurably improve task accuracy.

Year: 2026Generality: 350Added: Sep 21, 2026
Back to Vocab

EvoOntology is a self-evolving ontology layer for data agents, introduced by Meiduo Chong, Shaolei Zhang, Ju Fan, and Xiaoyong Du in "EvoOntology: A Self-Evolving Ontology Layer for Data Agents" (arXiv:2609.15779, September 2026). It addresses what the authors call the agent-data gap. An agent working over heterogeneous tables, files, and databases can normally only see that data through generic tools, such as listing column names or file paths one call at a time. Hand-written semantic layers pasted into a prompt do not scale to many data sources or adapt as the agent's behavior changes.

EvoOntology packages the ontology itself as an MCP server with three layers: a schema layer, a content layer, and a tool layer. A data agent queries it directly at runtime instead of reading a static description. A dedicated builder agent constructs the initial ontology autonomously, and a self-evolution loop then continuously revises it through small, typed edits. Each candidate edit is attributed to a specific weakness in the ontology and is kept only if a paired evaluation on the same underlying model shows it actually improves results, rather than being applied unconditionally.

Across three data-agent benchmarks and four backbone language models, EvoOntology outperforms both raw data exploration and hand-built semantic-layer baselines. On the DDR-Bench benchmark, average accuracy across six backbones rises by 17.8 points, from a 4.8-point gain on Qwen3.5-Flash to a 26.7-point gain on GPT-5.5. Execution accuracy on the BIRD benchmark rises by 7.4 points. The authors report that edits to the tool layer, rather than the schema or content layers, account for 57% of the total gain from evolution.

Sources

  1. EvoOntology: A Self-Evolving Ontology Layer for Data Agents

    arXiv · Sep 14, 2026

  2. ruc-datalab/EvoOntology (code repository)

    GitHub

  3. EvoOntology: A Self-Evolving Ontology Layer for Data Agents (HTML)

    arXiv · Sep 14, 2026

Research this in Signals

Scan EvoOntology for yourself.

Signals turns a topic into a sourced research record you can inspect and rerun. Your first scan is free, and this one starts with EvoOntology already loaded, so edit it or scan as is.