Triple

T26346497
Position Surface form Disambiguated ID Type / Status
Subject WWE European Championship E662788 entity
Predicate unificationMatchType P10212 FINISHED
Object title vs. title match LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: title vs. title match | Statement: [WWE European Championship, unificationMatchType, title vs. title match]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: unificationMatchType
Context triple: [WWE European Championship, unificationMatchType, title vs. title match]
  • A. unificationType
    Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
  • B. matchType chosen
    Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
  • C. typicalMatchType
    Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
  • D. usesMatchType
    Indicates that one entity applies or operates according to a specific type or category of matching criteria defined by another entity.
  • E. includesMatchType
    Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69ee81304194819092e20e0fae3aee07 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60fa718188190a3f4d76db2cdf670 completed May 2, 2026, 2:52 p.m.
PD Predicate disambiguation batch_69f602d2ec748190ae95154f34c7878f completed May 2, 2026, 1:57 p.m.
Created at: April 26, 2026, 10:42 p.m.