Triple

T2090291
Position Surface form Disambiguated ID Type / Status
Subject IIHF Division I World Championship E32651 entity
Predicate hasRelegationSystem P2678 FINISHED
Object true 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: true | Statement: [IIHF Division I World Championship, hasRelegationSystem, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRelegationSystem
Context triple: [IIHF Division I World Championship, hasRelegationSystem, true]
  • A. hasRelegationTo
    Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
  • B. hasRelegationPlayOff
    Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
  • C. hasRelegationHistory
    Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
  • D. hasPromotionRelegation
    Indicates that there is a system in which entities can move up (promotion) or down (relegation) between hierarchical levels based on defined criteria or performance.
  • E. relegationSystem chosen
    Indicates a system in which entities are moved to a lower tier or level based on their performance or ranking within a structured hierarchy.
  • 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_69a885eba0708190999696a45cbec816 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abba7443448190a2642769d0b5fb93 completed March 7, 2026, 5:41 a.m.
PD Predicate disambiguation batch_69abb7b4356881909217c42ccb8bb1ed completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.