From Concept to Prototype: Grounding AI & LLMs with Overture's Cross-Theme Knowledge Graph - Overture Maps Foundation

Search

Close Search

Blog

From Concept to Prototype: Grounding AI & LLMs with Overture’s Cross-Theme Knowledge Graph

By Albi WiedersbergJuly 22, 2026No Comments

LLMs are good with text and bad with coordinates, so they guess when asked where things are. Overture is testing whether map geometry itself can become the connective layer across data themes, giving AI a verifiable spatial graph to reason over. ORATOR, a prototype built by Overture member Wherobots, (led by Daniel Smith) generated 700,000 nodes and 1.2 million edges over the San Francisco Bay Area to see if the idea holds.

Geometry is the foreign key. If a place sits inside a building, the data already knows they are related. Nobody had to write that link by hand.

This effort is in the prototyping phase, and we want input from the Overture community before any of it hardens into a standard. The goal is a cross-theme knowledge graph that solves real problems for developers and AI engineers, not a clever demo.

A strategic pillar for AI readiness

Large language models process language well. Ask one to do raw coordinate math or reason about what is near what, and it starts to struggle. An AI agent routing a delivery or sizing up the businesses on a single city block needs more than a good vocabulary. It needs a structured, verifiable grounding layer it can trust.

Positioning Overture’s open map data and the Global Entity Reference System (GERS) for clean AI and LLM consumption is a core strategic priority for the foundation. A trusted source of geospatial facts and relationships is what stops a model from inventing spatial context when it does not actually know the answer.

The invisible conflation tax

Overture assembles high-quality data from many open sources across Places, Buildings, Addresses, Transportation, and Divisions. Open data arrives this way by nature: independent feeds, built by different communities for different purposes, with no shared keys linking a place to the building it occupies or a building to the road that serves it. Within a single theme, Overture already provides these links – Transportation and Divisions carry their own connective structure. The open question is how to link across themes, where the same real-world entity may show up as a point in one feed, a polygon in another, and a line in a third.

So a plain human question, like "which businesses operate inside this building footprint," forces developers to write their own spatial joins before an LLM can touch the data. That work gets repeated by every team that needs the same answer. We call this the conflation tax: a recurring cost the whole downstream ecosystem pays to rebuild relationships that the geometry already implies.

Every AI team grounding a model in the physical world ends up solving the same join problem. The conflation tax is what they pay to do it alone.

Weaving the graph: a conceptual prototype

To explore solutions, the Overture Product Council has been evaluating approaches to cross-theme linkage. As part of that work, Overture member Wherobots built an early-stage prototype called ORATOR (Overture Maps Foundation Knowledge Graph).

This is an experimental proof-of-concept, not a finished at-scale product. It is a testing ground for one question: how should spatial relationships be structured to serve AI workflows well? Wherobots has written up the broader technical pattern behind this work in Graph RAG for the Physical World, which walks through the spatial joins, storage, and graph traversal in detail.

ORATOR runs on pure spatial derivation. The working principle is that geometry acts as the foreign key. When a place point falls inside or near a building polygon, a spatial predicate turns that physical fact into a graph edge automatically.

Key features under test:

Relationships carry confidence scores. Strict containment earns a 1.0; weaker spatial signals score lower.

Fallback rules add hierarchy. An address inside the same building as a place beats an address that is merely closer in raw distance.

Every edge keeps full provenance, so a downstream model can trace exactly why and how two entities were connected.

Under the hood: testing the architecture

The prototype shows how separate themes might become a working spatial knowledge graph.

Six node types are derived from Overture’s core themes: building, place, address, connector, division, and a derived snap_point for road access.

Nodes connect through eight semantic relationship types, including located_in, has_address, and access.

An experimental MCP server exposes the graph to AI agents through query tools such as extract_subgraph and find_nearby, so a model receives structured knowledge rather than a pile of coordinates.

In a San Francisco Bay Area proof of concept, the pipeline produced more than 700K total nodes and 1.2M total edges in roughly 8...