How AI search resolves your brand to an entity — and the five layers that decide

AI search rarely reads your page as a bag of keywords. Before it cites anything, it tries to resolve the words into entities — real-world "things" in a knowledge graph, each with attributes and relationships — and decide which known entity your brand actually is. If it cannot resolve you to a thing, your sentences are tokens it can match but never truly know.

That gate sits underneath every citation decision, and most marketing teams never see it. They optimize copy for a query while the engine quietly asks a more basic question: is this brand a thing I recognize, and if so, which one? This piece traces how that resolution works, using the primary sources that describe it — entity-resolution patents from a spread of companies, the peer-reviewed entity-linking literature, and Google's own knowledge-graph disclosures — and closes with a single model, the Entity Authority Stack, plus an honest account of where the evidence stops.

Does AI search even know your brand is a thing?

The foundational move happened more than a decade before ChatGPT, and generative engines inherited its wiring.

In May 2012, Google introduced the Knowledge Graph as an intelligent model that "understands real-world entities and their relationships to one another: things, not strings," stating it then contained "more than 500 million objects, as well as more than 3.5 billion facts."[1] That sentence is the hinge. Search stopped being only about matching the characters in a query to the characters on a page and started maintaining a model of the things those characters refer to.

The plumbing that makes a brand a "thing" in an index is described, in different words, across a spread of patents — and the spread itself matters. Microsoft's "Knowledge-based entity detection and disambiguation" patent (US9665643B2) describes associating entity identifiers with a web page and storing them "as metadata of the page in a search engine index," which "will enable entity-based queries" and the ability to re-rank results by entity rather than keyword.[2] Read these patents as the vocabulary and mechanics of entity resolution as a field — Microsoft, Google, Amazon, and independents all describe variants of the same machinery. None is a sworn confession of what any specific 2026 engine ships in production; what they establish is that the levers are general and well-understood.

What happens when the model has never heard of you?

"Existence" has two faces, and conflating them is the most common mistake I see. One is whether you're a node in a graph the engine can look up. The other is whether the language model has parametrically learned you — whether your facts are baked into its weights. The peer-reviewed probes on the second face are humbling.

The LAMA probe showed that pretrained models store relational knowledge recoverable through fill-in-the-blank cloze statements with no fine-tuning[6] — so models do carry entity facts. But the coverage is brutally uneven by popularity. The PopQA study found that "scaling... fails to appreciably improve memorization of factual knowledge in the long tail," while retrieval augmentation helped significantly for low-popularity entities.[4] The Head-to-Tail benchmark, spanning 18,000 QA pairs across 16 models, concluded that "existing LLMs are still far from being perfect... especially for facts of torso-to-tail entities."[5]

The bridge between the two faces is the most actionable finding in this entire literature. The WildHallucinations benchmark — built from real entities mined from chatbot conversations — found that "about half" of its 7,919 entities "do not have associated Wikipedia pages," and that "LLMs consistently hallucinate more on entities without Wikipedia pages," across 118,785 generations from 15 models.[3] No structured presence is not a neutral starting point; it is the single highest-risk condition for being fabricated or ignored.

Most B2B brands live in that torso-to-tail. The lever is not "rank higher"; it is "become retrievable" — a graph node with enough corroboration that the engine looks you up rather than hallucinating you.

Which "Acme" are you?

Once a name can be resolved, the engine faces the next problem: names collide. There is an Acme that sells CRM software, an Acme that presses records, and an Acme that supplies anvils to cartoon coyotes. Disambiguation decides which one a given mention means.

The mechanism is context. Google's "Additive context model for entity resolution" patent (US9697475B1) describes resolving an ambiguous mention by building a vector of context features from the surrounding document and selecting the highest-scoring candidate entity.[7] The modern research version is dense and learned rather than hand-built. The BLINK system performs zero-shot entity linking by defining each entity through a short textual description, retrieving candidates with a bi-encoder and re-ranking them with a cross-encoder.[8] ReFinED folds mention detection, fine-grained typing, and disambiguation into a single pass and generalises to Wikidata, "which has around 15 times more entities than Wikipedia."[12]

There's a quiet asymmetry here worth naming. Microsoft's knowledge-graph query-expansion application (US20150095319A1) describes alias, disambiguation, filter, and ranking expansion segments, and notes that "when an identified entity is famous, renown, a celebrity, or simply unique a disambiguation segment may not be necessary."[9] The famous don't need to fight for disambiguation; the obscure do. Your lever is to make the context unmistakable — consistent category language, identifiers, and sameAs links — so the right Acme always wins the score.

What does the graph believe you are?

Resolving you to an entity isn't the same as knowing what you are. The attribute layer is the record the graph holds — your type, your founding, your category, your relationships — and, unusually, it's a record you can largely write.

Google is explicit that this is a brand-controlled lever. Its Organization structured-data documentation states that "some properties are used behind the scenes to disambiguate your organization from other organizations (like iso6523 and naics), while others can influence visual elements in Search results (such as which logo is shown in Search results and your knowledge panel)."[10]

Google's search results sometimes show information that comes from our Knowledge Graph, our database of billions of facts about people, places, and things.

Google also documents that content owners can suggest changes to knowledge panels they have claimed.[11] Taken together: the attributes you publish in structured form are the draft the graph edits. Leave them blank and the machine fills the record from whatever it can scrape — which is exactly how a wrong founding date or a stale description ends up in an AI answer with your name on it.

Who are you connected to?

Entities don't sit alone in the graph; they sit in a neighbourhood. What a model believes your brand relates to is learned from how often you co-occur with your category, its authorities, and its other entities.

The mechanism is geometric. The TransE method models relationships as translations over low-dimensional entity embeddings and "significantly outperforms state-of-the-art methods in link prediction on two knowledge bases."[13] The retrieval-era version assembles the neighbourhood on the fly. Microsoft Research's GraphRAG uses an LLM "to derive an entity knowledge graph from the source documents, then to pregenerate community summaries for all groups of closely related entities" — so closely-related entities become the unit of retrieval.[14]

What about evidence from the generative era itself? Here the strongest numbers come from vendor studies, and they should be read as direction, not proof. Ahrefs' study of 75,000 brands, using Spearman correlation, reported that "YouTube mentions show the strongest correlation with AI visibility (~0.737), outperforming every other factor across ChatGPT, AI Mode, and AI Overviews," ahead of branded web mentions and anchors.[15] Correlation is not causation, and a tool vendor has incentives — but the shape (off-site association beats on-page tuning) is consistent with how the graph is built. It also rhymes with the content-side finding that generative-engine optimization can lift a source's visibility "by up to 40%" through quotations, statistics, and citations rather than keywords[16] — a result we treat in depth in a companion piece, since it governs which retrieved candidate gets cited rather than how you become an entity.

Are you the entity it cites — or one it merely mentions?

The final layer is the one most brands never think about: among the entities the engine could name, which is central enough to actually cite? That's salience, and search systems have modeled it for years.

Microsoft's "Identifying salient items in documents" patent (US9251473B2) describes scoring an item's salience to a page using a soft function — roughly, the ratio of visits whose queries include the item to the total visits to that page.[17] Salience is the machine's formal answer to "is this page about the entity, or does it just mention it?" And prominence — being the entity worth surfacing — is scored across sources, not asserted on your own page. Google's location-prominence patent (US8046371B2) computes a score from factors including "the total number of documents referring to a business" and "the number of information documents that mention the business."[18] And its entity-metrics ranking patent (US10235423B2) describes ranking by combining knowledge-graph metrics — relatedness, notable entity type, contribution, and prize — with weights that depend on the type of entity.[20]

Where does the engine go to satisfy that salience? Increasingly, to you. Yext's study of 6.8 million AI citations across ChatGPT, Gemini, and Perplexity reported that 86% of citations came from sources brands already control, with first-party websites generating 44% of citations and listings 42%.[19] Own the definitive, structured page on your topic and the math compounds: highest salience, on a surface the engine already trusts to cite.

The Entity Authority Stack

Put the sources together and one model falls out. Five layers sit between a brand and a cited entity, and each has exactly one lever an operator controls.

To make it concrete, take a single, clearly-fictional brand and run it down the stack — what the engine asks at each layer, and the one move that wins it:

The pattern in that example is the pattern almost everywhere. Brands invest in the visible middle — attributes, copy, keywords — and skip the floor and the ceiling. They're legible but not authoritative: the model can resolve them, but never finds a reason to make them the cited entity. The advantage is bottom-heavy and top-heavy, exactly where no one is working.

What this means for the work

Three shifts follow directly from the evidence, in order of effort-to-impact.

Become resolvable before you become persuasive. A Wikidata item, consistent identifiers, and sameAs links across your real profiles turn an ambiguous string into a node the engine can look up. The probes are unanimous that retrieval against a structured record beats parametric guessing for everyone outside the head — and most brands are outside the head.

Write the record, don't leave it blank. Organization and Product structured data is the draft the graph edits. Publish your type, founding, category, and relationships in machine-readable form, or accept whatever the machine infers. This is the cheapest high-return work in the stack:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Tula Analytics",
  "sameAs": ["https://www.wikidata.org/wiki/Q000", "https://www.linkedin.com/company/…"],
  "foundingDate": "2019",
  "knowsAbout": ["product analytics", "retention measurement"]
}

Earn the neighbourhood and own the topic. Associations and salience are the layers that convert "known" into "cited." Be mentioned where your category is discussed — including video — and own one definitive page that the category treats as canonical. The measured signals are correlational, but they point the same way the mechanism does.

Where the evidence runs out

A serious reading marks its own edges. The patents here are disclosed methods in permissive drafting language, assigned to a mix of companies — Microsoft, Google, Amazon, NEC, and independents — and none is a sworn description of how a named 2026 engine resolves entities; they establish the field's mechanics, not any one vendor's production system. Several of the strongest mechanism sources — the location-prominence and salience patents, the KESM salience model — predate generative engines and describe classic information retrieval, applied here by analogy. And the generative-era evidence for the association and salience layers leans on two vendor studies (Ahrefs and Yext): large and original, but correlational and commercially motivated, not peer-reviewed causal proof.

What survives all of that is the shape. Engines resolve names to entities, disambiguate which entity you are, read the attributes the graph holds, weigh your associations, and judge your salience — and a brand that fails the early layers is never eligible for the late ones. Become a resolvable, well-described, well-connected, salient thing, and you compound across every engine that reads the graph next. Optimize a string, and you're betting the machine guesses right about a brand it was never taught.

— Sundar Ramesh Kumar · martech.llc