Triple
T214919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF Ice Hockey World Championship |
E4797
|
entity |
| Predicate | continentScope |
P9665
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [IIHF Ice Hockey World Championship, continentScope, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentScope Context triple: [IIHF Ice Hockey World Championship, continentScope, worldwide]
-
A.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
B.
continentOfUse
Indicates the continent where something is primarily used or in effect.
-
C.
countryScope
Indicates that something is limited to, applicable within, or defined at the level of a specific country.
-
D.
countryType
Indicates the classification or category of a country based on a specified typology (e.g., political, economic, or geographic type).
-
E.
borderedByContinent
Indicates that one entity has a land or maritime boundary directly adjacent to the specified continent.
- F. None of above. chosen
Provenance (4 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.