Triple
T662102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF World Championship |
E11777
|
entity |
| Predicate | hasRelegation |
P12779
|
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 World Championship, hasRelegation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelegation Context triple: [IIHF World Championship, hasRelegation, true]
-
A.
hasRelegationTo
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
B.
hasPromotionRelegation
chosen
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.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
canDelegateTo
Indicates that one entity has the authority or ability to transfer or assign its responsibilities, tasks, or decision-making power to another entity.
-
E.
hasAffiliate
Indicates that one entity is formally associated with another as an affiliate, typically through a partnership, membership, or subordinate organizational relationship.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.