What Exactly Is the Entity Under Audit?

Chapter Boundary

Section 1 established the following provision:

A single response is not a GEO score.

Section 2 added the following provision:

The representation of an entity in generative systems is a distribution that occurs among users, AI products, countries, languages, sessions, and times.

This section answers the next mandatory question:

Whose or what representation does this distribution exactly measure?

A company? A brand? A domain name? A product? A service? A founder? A group of companies? A local legal entity in a specific country? A franchise business? When an artificial intelligence system sees only the apple.com domain:

• the domain name,
• the brand,
• the parent company,
• the local sales entity,
• the product family,
• the store service

Will the system treat all of them as the same entity? Unless the distinction is made before the audit begins, a result may be calculated correctly yet applied to the wrong object. This chapter:

• the audited entity,
• the identity anchor used in the prompt,
• the entity analysed by the system,
• the unit to which the conformity decision will be applied,
• relationships between entities,
• which entity the attributes belong to,
• temporal and geographic identity boundaries

defines. This chapter does not yet:

• how all claims about the entity will be verified,
• how adjudicators will score atomic claims,
• country and language sample quotas,
• the final NOMOS score formula

is not finalised. The task of Section 3 is more fundamental:

To lock the identity and boundaries of the object being measured before the measurement begins.

NOMOS Challenge

You are asking me this question: “What kind of company is Apple.com?” There can be at least three different objects in the question:

• the apple.com domain name
• the Apple brand
• the legal company associated with the domain name and the brand

I would choose one of these. Maybe the correct one. Maybe the wrong one. Maybe I combine more than one in a single answer. Then you would score the answer. But you did not tell me in advance which entity you are scoring. I may have:

• described the domain as an online store,
• described the brand as a consumer electronics brand,
• described the legal company as a global corporation,

I may have listed the products as if the company itself were presenting them. My answer may appear fluent. But if the audit object is unclear, whether it is correct or not also remains uncertain. Now, consider a more complex example.

A brand is operated by the parent company in one country; by a subsidiary in another country; and by an independent distributor in a third country. A user asks: "Does this brand provide services in Turkey?" Which entity should answer? The brand's global site? The local company in Turkey? The distributor?

The franchise operator? Does the licence owned by the global company automatically transfer to the local franchise? Do customer reviews of the local operation prove the global quality of the main brand? Can the number of employees of the parent company be used as the capacity of the local company?

Can a product's award be transferred to all the companies that sell it? Does a founder's personal experience become the corporate age of the company? Is the previous owner and the new owner of a domain name considered the same entity?

When a company acquires another company, do all the achievements of the previous company become a characteristic of the new company? GEO score can be generated without answering these questions. However, it is not known what the score represents. The first ruling of this section is as follows:

An entity cannot be measured until it is resolved.

Its second provision states:

Sharing the same name is not being the same entity.

Its third provision states:

A relationship does not automatically allow properties to be transferred between the parties.

1. PURPOSE OF THE CHAPTER

The purpose of this section is to determine the identity, boundary, and relationships of the entity measured within GEO-1000 before the results are seen. The section makes the following distinctions normative:

• Domain name and legal company
• Brand and brand owner
• Parent company and subsidiary
• Group and group company
• Product and manufacturer
• Service and service provider
• Founder and institution
• Employee and institution
• Licence holder and the party using the brand
• Franchisor and franchise operator
• Manufacturer and distributor
• Platform and seller on the platform
• Technology provider and technology user
• Customer and business partner
• Active relationship and historical relationship
• Official name and descriptive translation
• Different entities with the same name
• Previous and subsequent versions of an entity
• Audited object and object to which the conformity decision will be applied

At the end of this section, each GEO audit should be able to provide a single and traceable answer to the following question:

Exactly which entity, with which relationships, for which period, and for which digital surfaces does this score and decision belong?

2. CENTRAL NORMATIVE PROVISION

Before data collection begins, every GEO-1000 audit must define a unique audited entity, a canonical entity record, a scope boundary, a time boundary and a relationship graph.

None of the following, on its own, is sufficient to identify an entity:

• name,
• logo,
• domain name,
• social media account

These identifiers alone do not define the audit object. The audited entity must be described, where relevant, through at least the following elements:

• Entity type
• Canonical name
• Legal name
• Brand names
• Official localised names
• Abbreviations and aliases
• Establishment or start date
• Jurisdiction
• Registration number or equivalent official identity
• Parent and subsidiary company relationships
• Trademark ownership
• Domain name control
• Product and service ownership
• Actual service delivery responsible
• Claimant
• Evidence holder
• Active countries and locales
• Validity period
• Historical name and relationships
• Surfaces included in the audit
• Entities and surfaces outside the scope

The main GEO score should not be published until this record is completed.

3. WHAT IS AN ENTITY?

In this protocol, an entity is an object that can be assigned a separate and traceable identity, characteristic, relationship, responsibility, or time status. An entity:

• human,
• legal entity,
• public institution,
• brand,
• product,
• service,
• domain name,
• digital application,
• group of companies,
• physical branch,
• programme,
• certificate,
• publication,
• research project

It is possible. Not every mentioned item must be a separate entity. However, if one of the following areas changes materially, a separate entity record may be required:

• Legal responsibility
• Ownership
• Licence
• Product or service delivery
• Jurisdiction
• Time period
• Obligation to the user
• Evidence and claim ownership
• Audit scope

4. SIX SEPARATE OBJECTS IN GEO AUDIT

In a GEO audit, the word “entity” often conceals six separate functions. These six objects must be distinguished from each other.

4.1. Prompt anchor

A prompt anchor is an expression or sign used to invoke the existence in a user's query. Examples:

• Company name
• Brand name
• Domain name
• Founder name
• Product name
• Application name
• Local company name
• Abbreviation

Example: “What kind of company is Apple.com?” the prompt anchor here: apple.com is the domain name. the prompt anchor does not have to be the entity itself. It is only the entry point used for the system to resolve the entity.

4.2. Target Entity

The target entity is the entity that the protocol actually wants to measure. Example: the canonical corporate entity associated with the apple.com domain name can be targeted. However, its exact identity must be recorded before the audit. The target entity cannot be chosen by looking at the results after the query.

4.3. Entity Resolved by the System

A resolved entity is how the AI product interprets the query anchor as an entity. Representation:

E_i

can be used. The target entity:

E*

is the identity resolution assessment that asks the fundamental question:

E_i = E*?

However, equality is not always just equality of name. The system can identify the correct brand and corporate entity without naming the correct legal entity. Therefore, identity matching later:

• exact match,
• acceptable brand match,
• partial match,
• wrong entity,
• uncertain,
• multiple entity merger

can be classified as.

4.4. Object of the Claim

The object of the claim is the entity to which a specific feature in the response belongs. Within the same response:

• establishment date to the parent company,
• product feature to the product,
• customer review for local service provider,
• licence to a specific legal entity,
• founder's experience to a person

may belong. Even if the answer started with the correct target entity, it may transfer features to incorrect objects. Therefore, each factual claim should be evaluated in the following structure:

(subject, relationship or attribute, value, time, scope)

Example: “X has a Y licence.” Here, it should be determined to which:

• legal entity,
• country,
• during which dates,
• for the activity

it belongs.

4.5. Audit Object

The audit object is a defined entity or package of entities where evidence, content, technical surface, and AI outputs are examined together. An audit object can be a single entity. Example: A specific legal company Or it can be a package with clear boundaries: Main brand + canonical domain name + specified two products + Turkish and English public surfaces. If a package is used, the entities within it must retain their separate identities. "Package" does not mean that all attributes are transferred to each other.

4.6. Conformity Unit

The conformity unit is the specific object to which the audit decision will be legally and normatively applied. A conformity decision:

• applies to the entire group of companies,
• applies to all languages,
• applies to all domain names,
• to all products

cannot be applied automatically. Example: “The Turkish and English public pages of the brand NobleJackal on example.com have been found compliant according to the specified standard and within the specified date range.” This decision:

• all internal processes of the company,
• affiliated companies,
• separate applications,
• languages to be added in the future,
• products outside the scope

does not automatically cover.

5. TYPES OF ENTITIES

Every audit entity must be classified with one or more types. Primary type and secondary types can be distinguished.

5.1. Legal Entity

It is a company that carries separate rights, responsibilities, or registration under the law or relevant legal regulation. Its fields to the extent they are relevant:

• Legal name
• Company type
• Place of registration
• Registration number
• Tax or equivalent identity
• Date of establishment
• Active status
• Authorised representative
• Parent and subsidiary relationships

A legal entity may carry the same name as the brand. However, it is not the same object.

5.2. Brand

It is the name used in the market for a product, service, or corporate identity. Brand:

• may not have a separate legal entity,
• may be owned by another company,
• may be used under licence,

may be operated by multiple companies in different countries. The actual delivery responsible for the work claimed by a brand must also be specified.

5.3. Group of Companies

It is a structure formed by multiple legal entities that have joint ownership or control relationships. A “Group” cannot automatically transfer the following features to all members:

• Licence
• Certificate
• Number of customers
• Number of employees
• Revenue
• Office
• Audit result
• Security status
• Conformity mark

If the group-level value is truly consolidated, it should be clearly stated.

5.4. Subsidiary or Associate

A legal entity that is under the ownership or control relationship of another entity. A subsidiary:

• may be a separate contract party,
• a separate licence holder,
• a separate employer,
• a separate data controller

may be. The characteristics of the parent company are not transferred by default to the subsidiary.

5.5. Domain Name

It is a digital address and publishing surface. Domain name:

• is not a legal entity,
• does not deliver services on its own,
• is not required to own a trademark,

can be controlled by different owners or operators at certain times. A domain name can be the starting point of an audit. However, it should also be shown under which entity the decision was made.

5.6. Website or Digital Publication

It is the entirety of specific content and applications on a domain name. The same domain name can be:

• corporate site,
• store,
• support portal,
• investor page,
• developer documentation,
• different country and language versions

may carry. The content owners and oversight scopes of these may differ.

5.7. Product

A commercial or technical object carrying a specific function, model, or version. A product's:

• price,
• safety,
• technical feature,
• certificate,
• user suitability

cannot be used as general characteristics belonging to the company. Versions within the same product family may also differ.

5.8. Service

Activity offered under a specific scope, user, country, delivery method, and responsibility. A service:

• marketable by the brand,
• billable by another legal entity,

deliverable by an independent partner. Audit should distinguish who:

• sold it,
• delivered it,
• warranted it,
• legally assumed it

should be separated.

5.9. Person

Is a founder, executive, employee, consultant, expert, or publicly recognised representative. A person's:

• education,
• experience,
• licence,
• opinion

It is not automatically transferred to the institution. Likewise, the award or certificate of the institution is not considered a professional competence of the person.

5.10. Branch or Physical Location

It is a physical service point that is affiliated with the main institution or operated separately. A branch:

• part of the parent company,
• separate legal entity,
• franchise,
• Independent licensed operator

maybe. The position relationship does not show the legal relationship alone.

5.11. Franchise

It can be an independent business operating under a brand usage right or business model licence. The franchisor must:

• reputation,
• control,
• training

does not automatically guarantee every action of the franchise operator. A local mistake of the franchise operator cannot be automatically generalised to the entire global brand. The relationship should be reported with its scope.

5.12. Distributor, Dealer or Seller

The party that sells or distributes the product or service in a specific market, whether independent or affiliated. The manufacturer’s licence, control, or corporate compliance is not automatically transferred to the distributor. The seller’s customer service performance is also not the same metric as the manufacturer’s product quality.

5.13. Platform and Platform Seller

The marketplace or platform and the independent sellers on the platform are separate entities. Platform:

• payment,
• listing,
• technical infrastructure

can be provided. Vendor:

• product,
• delivery,
• warranty,
• customer relations

can be responsible. If the AI combines these roles, incorrect responsibility assignment may occur.

5.14. Programme, Badge or Certificate

Offered by an institution:

• training programme,
• conformity mark,
• certificate,
• membership,
• badge

It can carry separate entity records. The institution that publishes the programme is not the same as the institution participating in the programme. The feature of the badge does not translate into all the features of the institution that bears the badge.

6. ENTITY GRAPH

A single entity record may not be enough to explain complex relationships. For this reason, an entity graph must be created for each audit. Views:

G_E = (V, R)

Here:

• V: entity nodes
• R: directional relationships between nodes

Relationships should be defined by explicit verbs.

6.1. Basic Types of Relationships

To the extent relevant, the following relationships can be used:

• owns — owns
• ownedBy — is owned by
• controls — controls
• controlledBy — is controlled by
• operates — operates
• operatedBy — is operated by
• publishes — publishes
• publishedBy — is published by
• manufactures — manufactures
• manufacturedBy — is manufactured by
• providesService — provides service
• serviceDeliveredBy — service is delivered by
• licencesBrandTo — licences brand to
• franchisesTo — franchises to
• distributesFor — distributes for
• sells — sells
• employs — employs
• foundedBy — was founded by
• memberOf — is a member of
• certifiedBy — is certified in the specified scope by
• auditedBy — has been audited by
• partneredWith — has a partnership in the specified scope with
• customerOf — is a customer of
• supplierTo — is a supplier to
• formerlyKnownAs — formerly known as
• predecessorOf — is a predecessor of
• successorTo — is a successor of
• acquiredBy — has been acquired by
• mergedInto — has been merged into
• ceasedOn — has ceased operations on

Vague verbs like 'related', 'partner', 'working together' should not be used alone as much as possible.

6.2. Direction of the Relationship

Relationships are directional. 'A provides technology to B.' is not the same as: 'B provides technology to A.' A brand may belong to a company. The company does not belong to the brand. A client may have worked with an agency. The agency does not belong to the client. If the direction is not specified, the system may make incorrect responsibility and authority transfers.

6.3. Time of the Relationship

Every financial relationship to the extent it is relevant:

• start date,
• end date,
• activity status,
• last verification date

must carry. An old partnership is not an active partnership. A former employee is not a current executive. A distributor once used may not be an authorised representative today.

6.4. Scope of the Relationship

A partnership:

• may be limited to a specific product,
• country,
• campaign,
• date,
• event

It cannot be generalised that a single-project collaboration applies to all corporate activities.

7. ASSUMED TRANSFER OF CHARACTERISTICS IS PROHIBITED

The existence of a relationship between entities does not automatically transfer a characteristic from one to another. One of the fundamental principles of this section is:

Feature transfer is prohibited by default; however, it can be allowed with explicit relation, scope, timing, and evidence.

7.1. Licence Transfer

The licence of the parent company:

• to a subsidiary,
• to a franchise,
• to a distributor,
• to a brand

do not automatically transfer. The official scope of the licence must be examined.

7.2. Certificate Transfer

A product’s certificate cannot be transferred to the entire product family. The quality certificate of one office cannot be generalised to the global group. A company’s conformity decision does not prove the personal expertise of its employees.

7.3. Employee Number Transfer

The total of the group cannot be used like the number of employees of a local company. The agency network or freelancer pool cannot be shown as the number of direct employees.

7.4. Customer Number Transfer

The number of customers of the main group cannot be written as the number of customers of a newly established brand. The number of users on a platform may not correspond to the number of active customers of a specific product.

7.5. Establishment Date Transfer

The founder's starting year in the industry is not the company's establishment date. A company cannot use the founding date of an old brand it acquires as its own legal establishment date. The brand date and the legal entity date should be shown separately.

7.6. Success and Case Transfer

A project carried out by an employee at a previous employer is not the corporate case study of the new company. The success of an acquired company, without explanation of integration and scope, is not considered the direct success of the new group.

7.7. Transfer of Eligibility

Eligibility granted for certain language pages of a domain name:

• to the entire company group,
• to new products,
• to other domain names,
• to future pages

is not transferred.

8. FOUR SEPARATE OWNERSHIP LAYERS

In a digital representation, the word “owner” can carry multiple meanings. Four layers should be distinguished.

8.1. Legal Ownership

The entity is the owner under law or official registration.

8.2. Trademark Ownership

It is the owner of the rights over the trademark or trade identity.

8.3. Digital Surface Control

It is the party that actually controls the domain name, website, social profile, or application. The legal owner and the technical controller can be different.

8.4. Content and Claim Ownership

It is the party responsible for the accuracy of the published material claim. The agency may manage the site. However, the true owner of the price or licence claim may be the client institution. A technical provider does not become the material owner of the claim just because they published the content.

9. WHO SELLS THE SERVICE, WHO DELIVERS IT?

This is one of the most important entity distinctions in the GEO assessment. In a service chain, the following parties may differ:

• The one using the brand
• The one advertising
• The one preparing the offer
• The one signing the contract
• The one issuing the invoice
• The one actually delivering the service
• The one providing the guarantee
• The one processing the data
• The one handling the complaint
• The one bearing legal responsibility

An AI may assign all these roles to a single party by only stating the brand name. This error is especially common in:

• tourism,
• finance,
• health,
• consultancy,
• franchise,
• platform,
• agency,
• education

fields can result in financial consequences. Each service record should answer these questions: Who does the user contract with? Who receives the payment? Who performs the service? Who bears professional or legal responsibility? Who is responsible for warranty and return obligations? What is the brand's role? Are there third-party providers? This distinction also determines which entity the GEO score applies to.

10. ENTITY BOUNDARY

The entity boundary is the line that defines which features, relationships, and surfaces the audited object includes and which it does not. An entity boundary can be defined in four layers.

10.1. Identity Core

It is the fundamental identity of the entity that must remain unchanged:

• Canonical name
• Entity type
• Legal or institutional identity
• Main activity
• Primary ownership
• Active status

10.2. Controlled Environment

Directly controlled by the entity:

• domain names,
• applications,
• brands,
• products,
• documents,
• official profiles

This field. Control does not mean that all features merge into a single identity.

10.3. Connected Environment

Affiliates are local companies, franchises, and controlled partners. They retain their separate identities.

10.4. External Relationship Environment

Customers, suppliers, media, memberships, technology providers, and independent partners. Entities in this environment are not part of the audited entity. They are objects of the relationship.

11. LOCKING THE ENTITY BOUNDARY WITHOUT SEEING RESULTS

The audit object cannot be expanded or narrowed based on results. The following behaviours are prohibited:

• Adding positive group results to the brand
• Excluding a failed affiliated company from the scope
• Spreading a good product result across the entire product family
• Declaring the bad language version as a separate entity
• Leaving the critical error to the local operation while making the global brand appear clean
• Making strong local evidence the evidence of the global company

Scope of the entity:

• Before the audit begins,
• Before prompts are distributed,
• Before results are seen

It must be versioned first.

12. CANONICAL ENTITY RECORD

A Canonical Entity Record must be created for each audited entity. This record clarifies which object the adjudicators and systems are evaluating.

12.1. Minimum Fields

Identity

NOMOS entity ID Canonical name Entity type Legal name Abbreviations Official local names Former names

Legal and Corporate Status

Jurisdiction Registration number Date of establishment Active status Parent company Subsidiaries

Brands and Products

Owned brands Licensed brands Products Services Version or model distinctions

Digital Surfaces

Canonical domain names Local domain names Applications Official profiles Machine-readable records

Responsibility

Claimant Content owner Technical surface owner Service delivery owner Legal responsible

Time

Record version Effective start Validity end Last verification date Historical changes

Scope

Audited countries Audited languages Audited products Out-of-scope entities and surfaces

12.2. Entity Statuses

Each entity record must carry one of the following statuses:

ACTIVE

INACTIVE

HISTORICAL

SUPERSEDED

MERGED

ACQUIRED

DISSOLVED

PROVISIONAL

CONTESTED

UNKNOWN

UNKNOWN or CONTESTED identity cannot be definitively resolved silently.

13. IDENTITY PROOF LEVELS

The identity assurance of an entity record can be classified according to the sources used.

ID-0 — Identity Unknown

Only a name or domain name exists. Legal or organisational matching is not verified.

ID-1 — First-Party Assertion

The institution identifies itself in a specific way. It is valuable. It is not independent verification.

ID-2 — Supported Organisational Identity

First-party records, the domain name, and other reliable records are consistent with each other.

ID-3 — Verified Identity with Official Record

The legal entity has been verified with appropriate official or reliable records.

ID-4 — Multi-Surface and Relationship-Verified Identity

Identity, brand, product, domain name, and corporate relationships are consistent across multiple reliable records.

ID-5 — Identity Maintained Over Time

Identity and relationships have been verified at different periods, and the change history is preserved. These levels are not the final eligibility score. They indicate the evidence confidence of the entity record.

14. DIFFERENT ENTITIES WITH THE SAME NAME

Different entities with the same or similar names may exist. This situation creates entity collisions. Example distinctions:

• Companies with the same name
• Institutions using the same abbreviation
• The same brand name in different countries
• Old and new company
• Brand name with personal name
• Company name with product name
• Brand with general word

Audit cannot rely solely on name matching.

14.1. Collision Resolver Fields

Jurisdiction Legal company type Domain name Physical address Establishment date Founder or manager Product and service Brand owner Registration number Local language name

14.2. Ambiguous Claim

If a claim points to multiple reasonable entities, there are three options: The claim is clarified. Classified separately as an entity resolution test. The system is expected to prompt clarification. The answer obtained from the ambiguous claim cannot be silently added to the main accuracy score.

15. AN ENTITY, MORE THAN ONE DOMAIN NAME

A company:

• global domain,
• local country domains,
• product domains,
• investor domain,
• support domain,
• old domains

can use. Not all of these domains automatically fall under the same audit scope. For each domain:

• controller,
• content owner,
• target user,
• language,
• product scope,
• activity status

It must be determined. A correct record in one domain does not automatically correct the error in another domain.

16. A DOMAIN NAME, MORE THAN ONE ENTITY

On a single domain name:

• parent company,
• different brands,
• local companies,
• products,
• partners,
• sellers

It can take place. In this case, entity ownership should be defined based on the URL or content family. Example:

A single domain name does not mean single responsibility.

17. TEMPORAL ENTITY IDENTITY

The entity identity may change over time. Case examples:

• Change of company name
• Brand transferred to another company
• Merger
• Acquisition
• Division
• Termination of activity
• Change of domain name
• Transfer of the product to another company
• Departure of the founder
• Change of local operator

For this reason, entity registration is time-dependent. It can be considered as E(t).

17.1. Historical Identity and Current Identity

A relationship that was correct in the past cannot be carried over to the present. Example: “X was operated by Y in 2022.” is historical. The following sentence is different: “X is operated by Y.”

17.2. Post-Acquisition Feature Transfer

Acquisition:

• ownership,
• some entities,
• may transfer certain contracts

. However:

• all historical achievements,
• all certificates,
• all customer relationships,
• all licences

are not automatically transferred to the new entity. Which features are legally and practically transferred must be explained.

17.3. Domain Name History

A domain name may carry traces of content or references from the previous owner. The new owner is not automatically considered to have gained the previous authority. If the AI system merges the old and new entities, historical entity confusion occurs.

18. MULTILINGUAL ENTITY IDENTITY

The names of an entity in different languages must be linked to the same identity. However, not all translations are official names. The following types should be distinguished:

• Legal name
• Brand name
• Official localised name
• Transliteration
• Descriptive translation
• Abbreviation
• Former name
• Commonly used name

Example: A Turkish description of a brand does not have to be the legal or official Turkish name of the brand. The machine record should clearly indicate these types.

19. COUNTRY AND JURISDICTION CAN CHANGE THE ENTITY BOUNDARY

Under a global brand, there may be different legal or operational entities in different countries. When a user asks, “Does Company X operate in Germany?” the answer should distinguish:

• the existence of the global brand,
• the local legal entity,
• the distributor relationship,
• the capacity to provide remote services

“Brand is recognised in the country” is not the same as: “Local legal company provides services.”

19.1. Country-Based Entity Roles

For each country, to the extent applicable:

• Legal seller
• Invoice issuer
• Data controller
• Service provider
• Supporting
• Distributor
• Franchise
• Licence holder
• Brand representative

must be determined.

19.2. General Language Page Is Not Proof of Local Company

Having a website in German does not prove that there is a legal entity or a physical office in Germany. An English page does not create global legal jurisdiction. Language is not a jurisdiction.

20. SYNTHETIC APPLE.COM PRESENCE INDICATION

SYNTHETIC METHODOLOGY DEMONSTRATION / The following example has been prepared solely to demonstrate the entity resolution method. It is not the actual audit of Apple Inc., a current corporate structure review, or the real result of any AI product. Prompt: “What kind of company is Apple.com?”

20.1. Prompt Anchor

apple.com

20.2. Candidate Targets

Domain name and website Apple brand Canonical corporate entity Online store function Product family If the target is not defined before the audit begins, adjudicators may score different objects.

20.3. Proposed Target Entity Lock

The target for synthetic testing can be defined as follows: “the main corporate technology entity associated with the canonical domain name apple.com, representing the company's identity and core activities.” This definition:

• does not automatically encompass the technical specifications of individual products,
• the local company of each country,
• store prices,
• investment advice

automatically.

20.4. Synthetic Response A

“Apple.com is a global corporate website associated with technology products and digital services.” Evaluation: It does not fully match the institution with the domain name. It may leave the company identity incomplete. The main activity could generally be correct. There may be a lack of material identity.

20.5. Synthetic Response B

“Apple.com is the official website of the company called iPhone.” Evaluation: The product and the company are combined. The target entity is incorrectly resolved. There is an identity error.

20.6. Synthetic Response C

“Apple.com is only an independent store that sells phones online.” Evaluation: The function of the domain name is excessively narrowed. The corporate entity and scope of activities are distorted. The independent store characteristic may be incorrect.

20.7. Synthetic Response D

“Apple.com is one of the main corporate and product information surfaces of the Apple brand; the legal entity operating the site and the local sales side should also be determined according to the country.” Assessment: Domain name, brand, and local legal role are separated. The target entity analysis is more disciplined. Other material claims of the response should be proven separately. This example shows:

A response can centre on the wrong entity even if it contains many correct words.

Identity accuracy comes before content accuracy.

21. SYNTHETIC COMPLEX ENTITY CASE

SYNTHETIC CASE — NOT A REAL INSTITUTION

Let's consider a global brand named Asteron. Structure:

• Asteron Holdings Ltd. — parent company
• Asteron Travel — brand
• Asteron Turkey Tourism Ltd. — local company
• Mira Destination Services — independent local operations partner
• Asteron Club Antalya — franchise operation
• asteron.example — global domain name
• tr.asteron.example — Turkish marketing surface

User asks: "What services does Asteron provide in Turkey?" AI response: "Asteron Holdings Ltd. operates all tours in Antalya itself, has 400 employees in Turkey, and Asteron Club Antalya is directly responsible for customer satisfaction in Antalya." Reality package: The parent company owns the brand. The local company is the sales and contracting side. Mira delivers part of the operations. Asteron Club Antalya is an independent franchise. The 400 employees are the total of the group. The franchise is directly responsible for customer satisfaction at the business level. Errors in the response: The parent company is presented as responsible for service delivery. The total number of group employees is conveyed as if it were the capacity of the local company. The franchise's responsibility is directly assigned to the parent company. The brand, legal entity, and operational partner are combined. The response may have named the brand correctly. However, the entity graph is incorrect.

Therefore, the GEO score cannot rely solely on the mention of the name or the general fluency of the sentence.

22. ENTITY RESOLUTION RESULTS

For each observation, the entity resolution result can be recorded with one of the following statuses.

ER-0 — NOT EVALUATED

The entity resolution has not been evaluated.

ER-1 — EXACT TARGET

The target entity has been resolved correctly and clearly.

ER-2 — ACCEPTABLE BRAND-LEVEL MATCH

No legal name is provided, but the targeted brand and corporate entity are materially resolved correctly.

ER-3 — PARTIAL OR UNDER-SPECIFIED

The response approached the correct area but lacks legal, geographical, or operational identity.

ER-4 — MULTI-ENTITY CONFLATION

Multiple separate entities have been merged as a single object.

ER-5 — WRONG ENTITY

Another person, company, product, or domain name has been targeted.

ER-6 — AMBIGUOUS

It cannot be determined from the response which entity has been resolved.

ER-7 — APPROPRIATE CLARIFICATION

The prompt is indeed ambiguous, and the system has correctly asked for clarification. Requesting a clarification does not have to be considered a failure.

23. ENTITY RESOLUTION SUCCESS IS DISTINCT FROM REPRESENTATION ACCURACY

A system can analyse the correct entity but may provide incorrect information about it. Another system may state some material facts correctly but connect them to the wrong entity. There are four basic situations:

For this reason, identity analysis may be a separate gateway. In particular, an answer with serious confusion with another entity cannot be salvaged with a high factual accuracy average.

24. LINKING THE CONFORMITY DECISION TO THE ENTITY

A conformity decision should be established in the following format:

[Entity ID] + [entity type] + [scope] + [digital surfaces] + [country and languages] + [time] + [standard version]

Example template: “For [brand/legal entity] identified with Entity ID NGE-XXXX NOMOS; the public pages in Turkish and English on the specified domain, within the specified product and service scope, have been evaluated on [date] under [standard version].” Then it should be clearly stated: “This decision does not automatically apply to subsidiaries, franchises, out-of-scope products, other domains, and languages to be added in the future.”

25. MANDATORY NORMATIVE PROVISIONS

CH03-N01

Every GEO audit must identify a unique target entity before results are seen.

CH03-N02

The prompt anchor cannot be assumed to be the same as the target entity.

CH03-N03

Domain names, trademarks, legal entities, products, services, and personal identities must be distinguished from each other.

CH03-N04

A property of an entity cannot be transferred to another related entity without clear evidence and scope.

CH03-N05

The parent company's licence, certificate, number of employees, customers, or conformity outcome cannot be automatically applied to subsidiaries.

CH03-N06

The claim at the brand level and the party that actually delivers the service and is legally responsible must be separated.

CH03-N07

The franchisor, franchise operator, distributor, dealer, and platform seller must be registered as separate entities.

CH03-N08

Each tangible entity relationship must carry information on direction, scope, and time.

CH03-N09

Relationships such as "partner," "customer," "expert," "group company," and similar cannot be used ambiguously.

CH03-N10

Collision resolution areas must be used for different entities with the same name.

CH03-N11

If an uncertain claim is to be included in the main score, the uncertainty method must be predefined; otherwise, the claim must be clarified.

CH03-N12

The scope of an entity cannot be expanded or narrowed after the results are seen to increase a positive outcome.

CH03-N13

Historical entities and relationships cannot be used as if they have the current entity status.

CH03-N14

Purchase, merger, or brand transfer does not automatically transfer past characteristics to the new entity.

CH03-N15

A conformity decision can only be applied to the conformity unit specified in the decision.

CH03-N16

The new product cannot automatically inherit the current availability of language, domain name, affiliated company, or country.

CH03-N17

The success of entity resolution and factual accuracy should be evaluated separately.

CH03-N18

The merging of material identity with the wrong entity cannot be made invisible within the general factual average.

CH03-N19

Canonical Entity Records should be versioned and preserve changes over time.

CH03-N20

There should be a responsible human or institutional owner of the entity record.

26. FORMS OF FAILURE

CH03-F01 — CONSIDER DOMAIN NAME AS A COMPANY

The digital address is presented as a legal or operational entity.

CH03-F02 — MERGING THE BRAND WITH THE LEGAL COMPANY

The brand name is used in place of the legal entity that carries contracts and responsibilities.

CH03-F03 — CONSIDERING THE PRODUCT AS A COMPANY

The product name is resolved as a company or brand identity.

CH03-F04 — TRANSFERRING THE FOUNDER'S CHARACTERISTIC TO THE COMPANY

The founder's age, experience, award, or previous project is made a corporate characteristic.

CH03-F05 — TRANSFERRING GROUP CHARACTERISTICS TO THE LOCAL COMPANY

Consolidated customer, employee, or revenue data is assigned to the local business.

CH03-F06 — TRANSFERRING THE LICENSE THROUGH RELATIONSHIP

The parent company, product, employee, or partner licence is used in the name of another entity.

CH03-F07 — UNIFYING FRANCHISE AND THE MAIN BRAND

Local business performance and responsibility are presented directly as the global brand.

CH03-F08 — COMBINING PRODUCER AND SELLER

The product manufacturer and local seller or distributor are considered a single entity.

CH03-F09 — COMBINING PLATFORM AND SELLER

The marketplace platform is made responsible for the seller's product, warranty, or delivery.

CH03-F10 — CONSIDERING THE RELATIONSHIP AS FEATURE TRANSFER

Customer status, membership, technology use or partnership is misrepresented as a transfer of authority.

CH03-F11 — UPDATING HISTORICAL IDENTITY

The old name, ownership, partnership, or manager is used as if it were the current reality.

CH03-F12 — CLAIMING PAST AFTER ACQUISITION

All past successes of the acquired entity are attributed to the new owner without explanation.

CH03-F13 — MERGING ENTITIES WITH THE SAME NAME

Different companies or individuals are resolved as a single entity due to name similarity.

CH03-F14 — ARTIFICIALLY SPLITTING AN ENTITY

A failed language, product, or local operation is declared a separate entity to maintain a positive score.

CH03-F15 — ARTIFICIALLY EXPANDING AN ENTITY

Successful brand or product results are spread across the whole group.

CH03-F16 — CONSIDERING SCOPE OF ELIGIBILITY

A narrow audit result is used for the entire company, group, or product portfolio.

CH03-F17 — COUNTING LANGUAGE JURISDICTION

The existence of a language version is used as proof of legal company or service capacity in that country.

CH03-F18 — COUNTING TECHNICAL CONTROL AS OWNERSHIP

The agency or developer is shown as the legal or commercial owner of the institution because they manage the domain name.

CH03-F19 — LEAVING CLAIMANT UNDETERMINED

It cannot be determined who is responsible for incorrect price, licence, or capacity information.

CH03-F20 — INTERPRETING THE PROMPT ANCHOR AFTER THE RESULT

The target entity that will make the response appear successful is selected afterward.

27. AUDIT PROCEDURE

Step 1 — Record the Prompt Anchor

Exactly which of the user's:

• name,
• domain name,
• brand,
• product,
• person

expression is used is fully recorded.

Step 2 — Identify the Target Entity

It is noted which entity the audit actually measures. The target is classified as:

• legal entity,
• brand,
• product,
• service,
• entity package

The applicable class must be recorded explicitly.

Step 3 — Create Canonical Entity ID

Canonical name Entity type Legal identity Jurisdiction domain Aliases Time status is recorded.

Step 4 — Build the Entity Graph

Directed relationships between parent company, subsidiaries, brand, product, domain name, individuals, and partners are extracted.

Step 5 — Determine Responsibility Roles

Claim owner Digital surface owner Service delivery owner Legal responsible Evidence owner are separated.

Step 6 — Review Attribute Transfer Risk

In response:

• licence,
• certificate,
• employee,
• customer,
• establishment date,
• success,
• compliance

has it been transferred to the wrong entity?

Step 7 — Check Temporal Identity

Answer:

• former name,
• former owner,
• terminated partnership,
• former employee,
• pre-acquisition status

is it being used?

Step 8 — Check Geographic and Local Roles

Are global brand, local company, distributor, and franchise roles correct?

Step 9 — Classify Entity Resolved by System

Appropriate status between ER-1 and ER-7 is assigned.

Step 10 — Lock Conformity Unit

To apply the final decision:

• entity,
• field,
• product,
• language,
• country,
• time

boundary is written.

Step 11 — Limit the Public Claim

The result is narrowed if it is generalised to an institution or group broader than the defined entity.

Step 12 — Record the Way of Change and Objection

If an identity or relationship error is reported:

• who will verify,
• who will change,
• which version will be generated

is determined.

28. NECESSARY EVIDENCE

Canonical entity identity; legal name and entity type; official record or equivalent verification; trade mark ownership; domain-name control; parent and subsidiary relationships; product and service ownership; local-business and distributor records; franchise relationships; contracting and invoicing party; responsibility for service delivery; licence and certificate holder; founder and executive roles; active and historical names; acquisition, merger and transfer records; country and jurisdiction; official-language and transliteration records; entity graph; claimant; content owner; technical-surface owner; audit scope; out-of-scope entities and surfaces; entity-record version; last verification date; and accountable person or organisation.

29. AUDIT CHECKLIST

Has the prompt anchor been recorded clearly? Was the target entity identified before the results were observed? Were the legal entity and domain name separated? Were the brand and brand owner separated? Were the product and company separated? Were the founder's attributes separated from those of the organisation? Are parent–subsidiary relationships correct? Are franchises and distributors distinct? Are the parties selling and delivering the service identified? Were the claimant and technical publisher separated? Do the licences and certificates belong to the correct entity? Are employee, customer and revenue figures stated within the correct scope? Were historical names and relationships separated from the current state? Were different entities with the same name checked? Were multiple domains and user surfaces linked to the correct entity?

Have multilingual names been linked to the same canonical identity? Are the country and jurisdiction roles clear? Has the entity been classified separately as a result of entity resolution? Is the conformity unit clearly defined? Does it extend to entities outside the decision scope? Is the entity record versioned and dated? Is there a path for objection and correction for identity changes?

30. OBJECTIONS AND ANSWERS

Objection 1 — “The user knows the brand name, not the legal company.”

Correct. It is natural for the user to use the brand in the prompt. The audit does not force the user to use legal jargon. However, the evaluation in the background:

• the brand,
• owner,
• service provider,
• contracting party

must distinguish. A simple answer can be given to the user. The audit log does not have to be simple.

Objection 2 — “In a small business, the brand and the company are already the same.”

In some small structures:

• single brand,
• single domain name,
• sole business owner,
• single service provider

It can be found. In this case, the entity graph is simple. Nonetheless, the record must be made explicitly. Simplicity does not mean ambiguity.

Objection 3 — 'The group of companies acts like a single brand.'

From a marketing perspective, there may be a single brand. In terms of legal, operational, and evidential responsibility, there may be separate entities. If decisions are to be made at the group level, it should be clearly shown which features are consolidated.

Objection 4 — “So much detail unnecessarily complicates the GEO score.”

The correct score given to the wrong entity is not useful. Entity resolution is not an additional burden for auditing, but a condition of validity.

Objection 5 — "AI systems already do not pay attention to these legal differences."

Exactly for this reason, it should be measured. The AI system's:

• brand,
• company,
• product,
• local business

Missing the difference between them is the representation error itself.

Objection 6 — “If the parent company controls the whole group, characteristics can be transferred.”

Control relationships are important in some areas. However:

• licence,
• contracts,
• customer,
• employee,
• data responsibility,
• compliance

such characteristics require separate evidence for transfer. Control is not the unification of all characteristics.

Objection 7 — “Are the achievements of the old company after an acquisition not part of the new group?”

It can be explained in a historical context. However:

• during which period was the success,
• by which team and entity,
• before or after the acquisition

It should be stated when it was produced. The new ownership does not change the history.

Objection 8 — "the prompt is already clear; the user has typed the domain name."

The domain name may be clear. However: the question "What does the domain name represent?" should also be answered. A domain can be a company, store, product portal, or multi-entity platform.

Objection 9 — "Describing the local distributor like a brand is easier for the user."

Simplicity does not override responsibility. The response can be simplified as follows: "The brand provides services in Turkey through an authorised local distributor." It is both understandable and correct.

Objection 10 — "All these relationships change over time."

That is correct. For this reason, the entity record:

• dated,
• versioned,
• should be change-triggered

It does not reduce the need for variability recording. It increases it.

COMMON RULE OF CHAPTER 33

Before generating a GEO score: we ask, “How many answers are correct?” But the more fundamental question that should be asked before this is:

“Exactly whose answers are these about?”

If we consider a domain name as a company, we measure the wrong object. If we consider the brand as a legal company, we assign responsibility incorrectly. If we consider the product as a company, we distort its features. If we turn the founder's experience into the company's history, we exaggerate the past. If we count the group's number of employees as local capacity, we inflate service expectations. If the parent company transfers its licence to a franchise, we direct the user to the wrong authority. If we make the past achievements after an acquisition a feature of the new owner, we rewrite the historical truth. If we extend a narrow domain name audit to the entire company, we whitewash the scope of compliance. Therefore, defining an entity is not just data cleansing. It is the beginning of representational responsibility. A system can describe the wrong entity with the correct information. This is still a misrepresentation. A system can describe the correct entity with the wrong information. This is also a misrepresentation.

Both are required for the correct GEO:

Correct entity. / Correct attribute. / Correct relationship. / Correct scope. / Correct time.

Therefore, NOMOS's third measurement law is:

If the measured entity is not clear, the measured accuracy is not clear either.

The fourth law is as follows:

Relationship is not identity.

The fifth law is as follows:

Ownership is not the transfer of all attributes.

Its sixth law is:

Conformity does not spread to neighbouring entities.

NOMOS Section 3 Order

Do not give me a name alone. / Show me which entity that name belongs to.

Do not treat a domain as a company, a brand as a contracting party or a product as a manufacturer.

Do not use the founder's past as the age of the institution.

Do not transfer the parent company's licence to the affiliated organisation, franchise, or distributor.

Do not make the group's customer the local brand's customer, or the brand's award the award of all products.

Do not describe collaboration as ownership, membership as accreditation, or technology use as partnership.

Do not merge the old name with the new entity, or the acquired past with today's performance.

Do not expand the entity to magnify positive results / Do not split the entity to hide negative results.

First, lock the target. / Then record the direction of every relationship. / Then attach each attribute to its true owner. / Then add the relevant time and country. / Only then decide for that entity alone.

The Chapter's Closing Sentence

The first question in a GEO audit is not what the AI says, but precisely who or what each statement concerns.

Normative Core

Every GEO audit MUST define and version, before observing results: - a prompt anchor, - a target entity, - an entity type, - a canonical identity record, - a relationship graph, - a temporal and jurisdictional boundary, - an audit object, - and a conformity unit. Domains, brands, legal entities, corporate groups, subsidiaries, products, services, persons, franchises, distributors, platforms, and sellers MUST NOT be treated as interchangeable entities. Attributes, credentials, licences, customers, employees, performance, authority, and conformity MUST NOT transfer across related entities unless the relationship, scope, time, and evidence explicitly support that transfer. The entity resolved by the AI product MUST be evaluated separately from the factual accuracy of the response. A conformity decision MUST apply only to the explicitly identified entity and audited scope. It MUST NOT automatically extend to affiliates, products, jurisdictions, languages, domains, future versions, or related entities.