Triple

T27879172
Position Surface form Disambiguated ID Type / Status
Subject Knockouts Division E705039 entity
Predicate hasSecondaryTitle P90082 FINISHED
Object Impact Knockouts World Tag Team Championship NE NERFINISHED

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: Impact Knockouts World Tag Team Championship | Statement: [Knockouts Division, hasSecondaryTitle, Impact Knockouts World Tag Team Championship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondaryTitle
Context triple: [Knockouts Division, hasSecondaryTitle, Impact Knockouts World Tag Team Championship]
  • A. hasSecondarySubject
    Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
  • B. hasPrimaryTitle
    Indicates that an entity is associated with its main or official title, distinguishing it from any alternative or secondary titles.
  • C. hasSecondary chosen
    Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
  • D. hasSecondarySee
    Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related entity.
  • E. secondSeriesTitle
    Indicates that an entity has a second series whose title is given by the related value.
  • 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_69ef84111bb4819084298f994b31c62f completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
Created at: April 27, 2026, 6:29 p.m.