TOPICALAUTHORITY.ORG TAO / ROOT

Entity Research Methodology

TOPICALAUTHORITY.ORG / METHODS / MTH-06STATE ENTITY RESOLUTION ACTIVE
MTH / 06 · IDENTITY · ATTRIBUTES · RELATIONS · EVIDENCE

Entity Research Methodology.

Entity research begins by deciding what a named thing refers to. Only after identity is resolved can a method assign a type, examine attributes, validate relationships, map evidence and determine whether a corpus represents that entity clearly, consistently and in the right context.

01 / MENTIONWhat string was observed?
02 / IDENTITYWhich real thing?
03 / TYPEWhat kind of entity?
04 / ATTRIBUTEWhich properties?
05 / RELATIONConnected to what?
06 / EVIDENCESupported where?
MTH / 06.1 OPERATIONAL DEFINITION

An entity is not merely a repeated word.

The same label may refer to several things; the same thing may be expressed through several labels. Entity research controls that many-to-many problem before counting coverage or constructing relationships.

TAO / DEFINITION
Entity research methodology is the controlled resolution and examination of distinct identities, their types, aliases, attributes, relations, contexts and supporting evidence across a declared information environment.
MENTION ≠ ENTITYA mention is observed text or markup.

An entity is the resolved thing that the mention is judged to represent under a documented identity rule.

ENTITY ≠ TOPICA topic organizes an area of meaning.

An entity is a distinguishable identity that can carry attributes and participate in relations.

RELATION ≠ CO-OCCURRENCETwo names on one page are not automatically connected.

A relation requires a defined predicate and evidence supporting that specific connection.

MTH / 06.2 IDENTITY DISTINCTIONS

Six objects that must never be collapsed.

Entity analysis becomes unreliable when strings, concepts, identities, documents and structured representations are treated as interchangeable.

01 / MENTION

Observed expression

A name, alias, abbreviation, pronoun, identifier or markup value found in an eligible source.

UNIT / EXPRESSION
02 / ENTITY

Resolved identity

The distinct person, organization, place, product, event, work or other thing represented by one or more mentions.

UNIT / IDENTITY
03 / TYPE

Declared classification

The analytical class assigned under a versioned type system, including allowed overlaps and unresolved cases.

UNIT / CLASS
04 / ATTRIBUTE

Property of an entity

A value or state describing the entity, with its evidence, time validity and conflict status preserved.

UNIT / PROPERTY
05 / RELATION

Directed connection

A subject–predicate–object statement whose direction, meaning, evidence and temporal scope are explicit.

UNIT / EDGE
06 / DOCUMENT

Evidence surface

A page or record can mention many entities. It does not become identical to the primary entity it describes.

UNIT / SOURCE SURFACE
MTH / 06.3 RESOLUTION PIPELINE

Identity is produced through inspectable decisions.

The pipeline preserves the path from raw expression to accepted entity record. An unresolved mention remains unresolved; it is never forced into the nearest candidate to improve completion.

01 / CAPTURE

Mention

Record exact expression, source location and surrounding context.

RAW / IMMUTABLE
02 / GENERATE

Candidates

Create plausible identities using aliases, identifiers and context.

SET / POSSIBLE
03 / COMPARE

Signals

Evaluate type, attributes, relations, time and contextual fit.

EVIDENCE / MULTIPLE
04 / DECIDE

Resolution

Accept, reject, merge, split or retain ambiguity under declared rules.

STATE / AUDITABLE
05 / TYPE

Classification

Assign permitted entity class and record competing types.

MODEL / VERSIONED
06 / LINK

Evidence

Attach each accepted property and relation to supporting observations.

CLAIM / TRACEABLE
07 / PUBLISH

Record

Freeze canonical identity, aliases, claims, conflicts and provenance.

ENTITY / INSPECTABLE
MTH / 06.4 INTERACTIVE ENTITY CONSOLE

One entity system. Four research operations.

Each operation uses a different analytical unit and produces a different permitted claim. All default console content is embedded in HTML and remains visible without JavaScript.

ENTITY PROTOCOL COMPILER / MTH-E06IDENTITY RESOLUTION ACTIVE
OPERATION / MENTION-TO-IDENTITY

Resolve an ambiguous label without forcing certainty

METHOD / SEALED
INPUT UNITOne mention with exact source context and eligible candidate identities
DECISION SIGNALSAlias, type, location, time, attributes, relations and document context
OUTPUT STATEResolved, unresolved, conflicting, merged, split or excluded
EVIDENCE RULEPreserve every supporting and contradicting observation used in the decision
HUMAN REVIEWRequired when decisive identity signals conflict or remain insufficient
VALID CLAIMThis mention was resolved to entity E-042 under identity rules version 1
NOT PERMITTED / A matching name alone does not establish identity, equivalence, ownership or relationship.
MTH / 06.5 RELATION LOGIC

An edge is a claim, not a decorative line.

Every relation must declare direction, predicate, evidence and temporal state. Reversing an edge or changing its predicate creates a different claim.

RELATION / 01 · OWNERSHIP
Organization ADomain B
predicate / owns

Requires evidence of ownership. A link, mention or shared branding alone does not establish legal or operational ownership.

RELATION / 02 · PRODUCTION
Company CProduct D
predicate / produces

Different from distributes, sells, repairs or mentions. Predicate precision protects the identity graph from semantic inflation.

RELATION / 03 · TOPIC ROLE
Page EEntity F
predicate / primary_subject

Different from incidental mention. Corpus ownership rules determine which document is responsible for the entity’s central explanation.

MTH / 06.6 EVIDENCE STATES

Entity claims require typed evidence states.

The record distinguishes what is directly observed from what is derived, inferred, contradicted or unresolved.

STATEMEANINGEXAMPLEALLOWED USEPROHIBITED COLLAPSE
ObservedDirectly present in eligible sourceExact name or identifier appearsMENTION EVIDENCEObserved mention → confirmed identity
ResolvedIdentity decision satisfies declared rulesMention maps to E-042ENTITY AGGREGATIONResolved here → universally identical
DerivedCalculated from validated entity recordsAttribute coverage rateTRANSPARENT METRICDerived score → external fact
InferredReasoned interpretation with alternativesLikely document ownerQUALIFIED ANALYSISLikely → established
ContradictedEligible evidence supports incompatible statesTwo founding datesCONFLICT REGISTERSelect preferred value silently
UnresolvedEvidence cannot distinguish candidatesShared name, weak contextREVIEW QUEUEUnknown → absent or false
MTH / 06.7 DERIVED MEASURES

Measure the corpus without inventing an authority score.

These TAO measures describe the declared entity model and analyzed corpus. Formulas, denominators and unresolved states remain visible.

MEASURE / 01

Resolution rate

resolved eligible mentions ÷ all eligible mentions

Reports how much of the mention population has passed identity resolution.

QUALITY / IDENTITY PIPELINE
MEASURE / 02

Entity representation rate

represented required entities ÷ required model entities

Requires a versioned entity model and explicit threshold for what counts as represented.

COVERAGE / MODEL VS CORPUS
MEASURE / 03

Attribute coverage

supported required attributes ÷ required attributes

Count supported values separately from mentions, nulls, contradictions and unresolved attributes.

COVERAGE / PROPERTY SET
MEASURE / 04

Relation coverage

supported required relations ÷ required relations

Predicate and direction must match. Co-occurrence does not satisfy the denominator.

COVERAGE / EDGE SET
MEASURE / 05

Conflict rate

entities with unresolved conflicts ÷ reviewed entities

Higher conflict visibility may reflect better auditing, not worse content.

QUALITY / DO NOT HIDE
MEASURE / 06

Document orphan rate

entities without a responsible document ÷ required entities

Uses declared ownership rules to find entities scattered across mentions but explained nowhere.

ARCHITECTURE / OWNERSHIP
MTH / 06.8 WORKED EXAMPLES

Concrete decisions with strict inference boundaries.

All examples are synthetic. They demonstrate method logic rather than live entity facts or external system states.

ID
EXAMPLE / 01 · AMBIGUOUS NAMEResolve “Atlas” across competing candidates
ILLUSTRATIVE
MENTION“Atlas launched a new research interface.”
CANDIDATESSoftware product, publisher or unrelated organization.
DECISIVE SIGNALSProduct URL, organization relation and release context.
OUTPUTResolve only if evidence distinguishes one candidate.
LIMIT / NAME MATCH ALONE IS NOT IDENTITY EVIDENCE
ATR
EXAMPLE / 02 · ATTRIBUTE CONFLICTTwo sources report different launch dates
ILLUSTRATIVE
ENTITYOne identity resolved through stable identifiers.
CONFLICTSource A: 2018; Source B: 2019.
CONTROLDistinguish incorporation, launch and public release.
OUTPUTPreserve both claims until predicate meaning is resolved.
LIMIT / CONFLICT IS DATA; DO NOT SILENTLY SELECT THE CONVENIENT VALUE
REL
EXAMPLE / 03 · RELATION PRECISIONProducer, distributor and seller are different edges
ILLUSTRATIVE
OBSERVEDA company page displays a product.
POSSIBILITIESProduces, distributes, sells, services or references.
CONTROLRequire evidence for the specific predicate.
OUTPUTRecord only the supported directional relation.
LIMIT / PAGE CO-OCCURRENCE DOES NOT DEFINE THE BUSINESS RELATIONSHIP
OWN
EXAMPLE / 04 · CORPUS OWNERSHIPAn entity is mentioned widely but explained nowhere
ILLUSTRATIVE
OBSERVEDEntity appears on 14 supporting pages.
ABSENTNo canonical page owns its definition and relations.
DERIVEDEntity enters the document-orphan register.
DECISIONAssign ownership or justify distributed treatment.
LIMIT / A NEW PAGE IS AN ARCHITECTURAL DECISION, NOT AN AUTOMATIC METRIC OUTPUT
MTH / 06.9 CONFLICT SURFACE

Strong entity systems preserve what they cannot resolve.

Forcing every input into a clean graph creates false certainty. These failure modes remain first-class research states.

CONFLICT / 01

Homonym collision

One label refers to several identities and context is insufficient to choose.

STATE / UNRESOLVED CANDIDATES
CONFLICT / 02

Alias fragmentation

Several labels for one entity are counted as distinct identities.

STATE / MERGE REVIEW
CONFLICT / 03

Type drift

The entity class changes across analysis without a versioned rule or valid multi-type state.

STATE / TAXONOMY CONFLICT
CONFLICT / 04

Predicate inflation

A weak mention is converted into ownership, production, endorsement or another stronger relation.

STATE / EDGE REJECTED
CONFLICT / 05

Temporal collision

Attributes valid at different times are treated as simultaneous contradictions.

STATE / VALIDITY WINDOW
CONFLICT / 06

Source circularity

Several pages repeat one unsupported origin and are misread as independent confirmation.

STATE / ORIGIN TRACE
CONFLICT / 07

Entity-page collapse

A document identifier is treated as the identity of the entity described by the document.

STATE / LAYER SEPARATION
CONFLICT / 08

Authority fiction

An internal coverage score is presented as external proof that a system recognizes or trusts the entity.

STATE / CLAIM REJECTED
MTH / 06.10 ENTITY MANIFEST

Every entity record should be reconstructable.

The manifest preserves identity logic, evidence state, conflicts and corpus responsibility as part of the research output.

ENTITY RECORD / MTH06-ENTITY-V1
01 / ENTITY IDStable internal identitycanonical id + record version
02 / LABELSCanonical name and aliaseslanguage + context + validity
03 / TYPEDeclared entity classtaxonomy version + conflicts
04 / ATTRIBUTESProperty claimsvalue + evidence + time state
05 / RELATIONSDirected entity edgessubject + predicate + object
06 / MENTIONSObserved expressionssource + context + resolution state
07 / EVIDENCESupporting observationsorigin + collected_at + claim link
08 / CONFLICTSUnresolved alternativescompeting state + review decision
09 / OWNERSHIPResponsible documentprimary + supporting + orphan state
MTH / 06 · ENTITY PRINCIPLE

A name is an observation. Identity is a research decision.

Strong entity research preserves the path from mention to identity, the evidence behind every property and relation, and the conflicts that prevent a clean conclusion.

TOPICALAUTHORITY.ORG / METHODS / MTH-06MENTION → IDENTITY → TYPE → CLAIM → EVIDENCE → GRAPH
TAO / CONTACT · DIRECT TRANSMISSION Have an asset, domain or market position to investigate? ENTER CONTACT SYSTEM →
DIGITAL ASSET INTELLIGENCE + EXECUTION
EXECUTED BY
BB DIGITALNA AGENCIJA

Investigation, consulting and execution of digital assets, premium-domain strategies, information architecture, semantic systems, websites and agreed digital growth plans.

TOPICALAUTHORITY.ORG / SEMANTIC INTELLIGENCE SYSTEM BB DIGITALNA AGENCIJA / BB.HR