Search engines and AI tools like ChatGPT no longer just match the words on a page — they try to recognize the real people, places, programs, and organizations those words refer to. This guide explains what an "entity" is, why it matters for whether your organization gets found and described correctly, and what a small team can do about it.
By Matt·Updated July 9, 2026
Quick answer
What is an entity?
An entity is a distinct, uniquely identifiable person, place, organization, or thing — as opposed to a keyword, which is just a string of text. Search engines and AI tools track entities, not keywords, to work out what your content is actually about and who or what it's referring to.
A keyword is just letters on a page (m-a-r-s). An entity is the real thing those letters point to — Mars the planet, Mars the Roman god, or Mars the candy company. Search engines and AI assistants map your text to entities first, then answer based on what they know about that specific thing, not the words alone.
Why entities matter
Search used to mean matching the words in a query to the words on a page. Today it means something closer to understanding: a search engine or AI assistant tries to work out which specific person, place, program, or organization you're asking about, then answers based on what it knows about that one thing — not on how many times a word appears.
This matters most for small organizations. If an AI tool can't tell your food bank's weekend meal program apart from a similarly named program at another nonprofit, it may describe the wrong one, mix up the details, or leave you out of the answer entirely. Getting your own entities right is largely a matter of clarity and consistency, not budget — see what AI search is for the broader shift this fits into.
The benefits
Improved accuracy. Whether someone searches "county library weekend hours" or asks an AI tool the same thing conversationally, an entity-based system can match the question to the right library, not just the right words.
Contextual intelligence. Systems that understand entities pick up on nuance better, which shows up in more accurate voice search results and conversational answers.
Easier fact-checking. AI tools can check what they're about to say against a knowledge graph's existing facts, which helps catch some errors before they reach the reader.
Content that holds up over time. Writing that's clearly about a specific program or person stays useful across different search engines and AI tools, instead of depending on one search term staying popular.
Key concepts and components
A handful of terms come up constantly once you start looking at how machines track entities. Here's what each one means in plain language.
Knowledge graph
A database of real-world entities and how they relate to each other — who works where, which program belongs to which organization, which city is the capital of which country. Search engines use it to answer questions directly, sometimes without sending the person to any website at all.
Nodes and edges
In a knowledge graph, a node is an entity itself; an edge is the relationship connecting two nodes (for example, "works at" or "is located in"). How densely two things are connected helps a system judge how closely related they are.
Schema markup (structured data)
Code you add to your own pages that spells out, in a standard format, exactly which entities and attributes are on that page. It removes guesswork — see structured data for beginners for how to add it without writing any code yourself.
Entity resolution and disambiguation
The process of figuring out which specific entity a word refers to when it could mean more than one thing. This is what stops a search for "Apple" from returning orchard-growing advice instead of the technology company.
Uniqueness
An entity refers to one specific thing. That's what separates it from an ambiguous word or a name two different things happen to share.
Attributes and relationships
An entity has properties that describe it (a person's title, a program's start date, a building's address) and links to other entities (a staff member works at an organization; an organization runs a program). The more of these you make explicit, the less a machine has to guess.
How entities work in information retrieval
Turning a page of plain text into a mapped-out set of entities happens in a fairly consistent sequence.
1
Named entity recognition
Software scans a piece of text and pulls out the words that represent specific entities, sorting them into rough buckets like people, places, dates, or organizations.
2
Disambiguation
The system looks at the surrounding words and checks its existing knowledge base to work out exactly which entity a name refers to — which "Jane Whitfield," which "Riverside," which "Harvest Table."
3
Relationship mapping
The system breaks sentences into simple subject–action–object statements (a founder started an organization) to capture exactly how the entities it found relate to each other.
4
Knowledge graph integration
The newly extracted entities and relationships are checked against what the system already knows. If the information is new and comes from a source it trusts, its knowledge graph is updated.
5
Query matching and answers
When someone asks a question, the system translates it into the entities it recognizes and answers using what it has mapped about them — as a direct answer, a widget, or a list of relevant pages. Both traditional search and tools like ChatGPT rely on some version of this pipeline; see how ChatGPT finds information for a closer look at one of them.
What entity confusion looks like in practice
Two scenarios showing how this plays out for small organizations — and what fixes it.
The historical society with two Janes
The problem
A county historical society was founded by Jane Whitfield. A completely unrelated novelist shares the same name. When people ask an AI tool "who founded the county historical society," it sometimes answers with facts about the novelist instead.
The fix
The society adds a short bio page for its founder with clear, specific facts — her actual role, years active, and organization — and marks it up with Person schema. Within a few weeks, answers about "who founded" the society start citing the right Jane.
The lesson: disambiguation isn't just something Google has to solve on its own — it's a page you can build yourself.
The food bank versus its own gala
The problem
A regional food bank calls its one-night annual fundraiser "Harvest Table" — the same name as its year-round weekly meal program. AI tools merge the two into one entity, describing the fundraiser as a standing weekly service.
The fix
The food bank gives each page its own specific title, adds Event schema to the fundraiser page and a separate program description to the meal program page, and links between them using anchor text that names each one distinctly. The two stop being conflated in later answers.
The lesson: the simplest fix is usually the right one — give related-but-different things clearly different, specific names on the page itself.
Where entity systems fall short
Entity systems are powerful, but they're not complete or unbiased. Three limits worth keeping in mind.
Scale and lag. Keeping a graph of billions of entities current takes enormous processing power, and new organizations, programs, and public figures appear daily. There's usually a real delay between something existing in the world and a search engine or AI tool fully recognizing it.
Facts versus opinions. Knowledge graphs are good at objective facts (a city's location, an organization's founding year) and much worse at anything subjective or contested (which nonprofit does the best work in a county). Don't expect entity systems to settle debates — only to get the facts right.
Bias in, bias out. If the source material a knowledge graph was built from contains errors or skewed coverage — for example, better documentation of large organizations than small ones — the system will tend to repeat that imbalance in its answers.
None of this is a reason to skip entity work. It's a reason to focus on the part you can actually control: making sure your own organization's people, places, and programs are unambiguous wherever they appear.
Make your own entities easier to recognize
Five concrete steps, none of which require a paid tool.
This isn't a new idea Google is still testing. In 2012, Google's own announcement of its Knowledge Graph summed up the shift as moving from "strings" to "things" — and every major AI tool built since has followed the same logic. If you'd rather have missing or unclear entities on your own site found for you, our find missing organizational information guide walks through a manual check.
Common questions
What is the difference between an entity and a concept?
An entity is a distinct, uniquely identifiable thing — your organization, a specific person, a specific event. A concept is a broader, more abstract category, like "architecture" or "food insecurity." In practice, most knowledge graphs treat concepts as a type of entity too, just a more general one.
How do search engines discover new entities?
By continuously crawling web pages, processing news and social media, and reading structured data (schema markup) that website owners add to their own pages. A new program or a new staff member becomes an entity once it appears clearly and consistently enough for these systems to notice it.
Does our organization need a Wikipedia page to be treated as an entity?
No. A Wikipedia page is a strong signal, but search engines and AI tools recognize millions of small nonprofits, local agencies, and individuals as entities based on ordinary web mentions and schema markup alone. A Wikipedia page helps; it isn't a requirement.
What does natural language processing (NLP) have to do with this?
NLP is the technology that lets software read a sentence, understand its grammar, and pull out which words refer to real people, places, or things. It's the mechanism underneath entity recognition — you don't need to understand it to benefit from writing clearly, which is what it rewards.
Does this mean we should stop doing keyword research?
Not stop — reframe. Instead of hunting for exact-match search phrases, list the real programs, people, and questions your community asks about, and write content that covers each one thoroughly. The specific wording matters far less than making sure the topic itself is covered well.