Observed Signal · Aug 12, 2026 · Technical Article · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Ontologies, Taxonomies, and Schemas Explained
This technical article explains the differences between controlled vocabularies, taxonomies, and ontologies for knowledge graphs. A controlled vocabulary is a closed list of defined terms; a taxonomy arranges those terms with broader/narrower relations (SKOS) to enable roll-up queries; and an ontology (RDFS/OWL) adds axioms and property semantics so a reasoner can derive facts. The author warns that ontologies are costlier to build and maintain, that RDFS/OWL operate under an open-world assumption (so domain/range declarations infer types rather than validate), and that validation (e.g., SHACL) is usually what teams want to prevent bad data. Recommended pragmatic practice: start with vocabularies and taxonomies, add minimal ontology features where they materially save work, and reserve full reasoning for interchange scenarios.
Practical guidance for designing knowledge graphs and validation vs. reasoning is relevant to data engineering and enterprise data-layer design; useful but not industry-shifting.
Track multigrid.ai Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- A controlled vocabulary is a closed list of permitted terms with identifiers, definitions, owners, and statuses.
- A taxonomy adds broader/narrower relations (commonly via SKOS) to enable hierarchical roll-up and faceted navigation.
- An ontology (RDFS/OWL) includes classes, properties (with domain/range), and axioms that allow automated inference and reasoning.
- RDFS/OWL use an open-world assumption: domain/range declarations infer types rather than act as validators.
- SHACL is the RDF-world validation language used to enforce closed-world constraints and report violations.
Connected Companies & Entities
1 Entity mapped“the article links to 'a glossary your company and your model both use' hosted at https://multigrid.ai/learn/shared-glossary....”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
AI Agents Revive Ontologies and the Semantic Web
AI engineers and researchers are revisiting ontologies and Semantic Web technologies to provide logical guardrails for agentic systems built on large language models. At the AI Engineer World’s Fair, UC Berkeley professor Frank Coyle and Neo4j CEO Emil Eifrem argued that ontologies—described as "data as graphs"—can validate reasoning, enforce rules (e.g., OWL axioms), and enable a shared semantic layer for thinner, scalable agents. Practitioners like Kingsley Idehen (OpenLink Software) are combining RDF memory and Semantic Web stacks with agents, while developers suggest agents could maintain and update ontologies during operation. The article frames this as a 2026 revival of software engineering discipline focused on quality control for loop engineering in agent systems.
2asy.ai Builds Cross-Domain Ontology Graph for Tariff News
2asy.ai updated its tariff briefing pipeline, moving from plain vector RAG to per-article graph extraction and now to a cross-domain ontology Graph RAG. The system extracts entities, events, and relations against a shared ontology, resolves entities across documents, and exposes a causal graph on the latest briefing (June 2 story). The author notes the current graph is sparse but will densify as more documents are ingested. The pipeline runs on local hardware (RTX 4090 and an AMD W6800) using open models and no cloud inference. The new approach enables connections and causal chains that plain vector similarity retrieval could not represent across a corpus.
Vector Database vs Knowledge Graph for LLMs
A practical guide comparing vector databases and knowledge graphs as storage backends for LLM applications. The article explains that vector databases (e.g., Qdrant, pgvector, Pinecone) store embeddings and excel at semantic similarity queries, while knowledge graphs (e.g., Neo4j, RDF stores) model entities and relationships and support exact, multi-hop relational queries. The author argues most real-world LLM systems need a hybrid: vectors for retrieval and graphs for precise reasoning and auditability (a pattern exemplified by Microsoft’s GraphRAG). Tool-level trade-offs, operational costs, and a four-question decision rule are provided to help teams choose the right architecture for their queries.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.