Methodology

Blazoom treats each subject as an entity with a stable slug, a type, aliases, and external identifiers.

Resolution

Incoming records match first on an authoritative external ID (such as a Wikidata QID), then on a known alias plus type, then on a normalized name plus type. A shared name alone is not enough to merge two people.

Facts and conflicts

Facts are typed (text, date, number, entity). If a new source repeats the same value, Blazoom attaches another citation. If it disagrees, both values are kept and a conflict is recorded unless a clearly more authoritative source replaces the primary value under written policy.

Relationships and merges

Relationships are labeled from a controlled vocabulary and can be sourced. Duplicate entities are merged rather than deleted; the losing slug redirects to the survivor.

Search

Ranking prefers exact names, then aliases, prefixes, tokens, and light typo candidates over a small prefix set. Importance and completeness can nudge order. Search result pages are not indexed.

Freshness

Birth dates are treated as static. Roles and websites refresh more often. Live prices and tour calendars are out of scope for this foundation.