Tech Meridian ← ENTITY INDEX
PROMY MERIDIAN RU

TOPIC · ENTITY #1593

knowledge graphs

Related event timeline, sources and context from the news index.

EVENT TIMELINE

3

RESEARCH · 1 SOURCE · arXiv cs.AI

What Does an Ontology Catch? arXiv:2610.37809v1 — Comparing curated, LLM-generated and data-derived ontologies as checkers for LLM agents

This paper studies ontologies themselves as checkers of LLM agents answering questions over knowledge graphs, comparing curated, LLM-generated and data-derived schemas used as prompt context, as checkers, or both. Evaluated on public graphs, UniProt and a private graph of ~10^9 triples across open-weight and proprietary agents, the authors quantify trade-offs between caught errors and false alarms, show curated schemas can contradict their data and often flag many correct answers, and examine whether combining sources or giving agents checker-specific feedback helps.

6.0

COMPANIES · 1 SOURCE · MIT Technology Review AI

MIT Technology Review Insights urges 'agentic shift' to scale enterprise AI

A sponsored report from MIT Technology Review Insights argues enterprises must move from treating AI as a tool to adopting an 'agentic shift' — an operating model that links people, processes, and data in real time. The piece recommends rebuilding data infrastructure for accessibility, adopting composable architectures, and ensuring data/model sovereignty, and notes fragmentation in enterprise systems and a projected $2.5 trillion in global AI investment by 2026.

6.0

CODING · 1 SOURCE · InfoQ AI, ML & Data Engineering

Presentation: From Retrieval to Reasoning — Building Production Agentic AI Systems with Knowledge Graphs

Cassie Shum argues that knowledge graphs are a foundational component for agentic AI systems and outlines four practical architectural patterns — context bundling, decision provenance, code as truth, and agent visibility. She also demonstrates an engineering harness built on a knowledge graph aimed at streamlining feedback loops, optimizing token usage, and improving system reliability.

5.0