Triple
T11271436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1960 IIHF World Championship |
E266821
|
entity |
| Predicate | editionOfOlympicTournament |
P98859
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [1960 IIHF World Championship, editionOfOlympicTournament, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionOfOlympicTournament Context triple: [1960 IIHF World Championship, editionOfOlympicTournament, 9]
-
A.
editionOfCompetition
Indicates that one entity is a specific edition or iteration of a recurring competition or tournament.
-
B.
paralympicGamesEdition
Indicates the specific edition of the Paralympic Games in which an entity (such as an athlete, event, or result) is involved or to which it is related.
-
C.
hasOlympicGamesEdition
Indicates that a particular edition of the Olympic Games is associated with or held by a given entity (such as a city, country, or organizing body).
-
D.
olympicGames
Indicates that an entity is an edition or instance of the Olympic Games event.
-
E.
olympicGamesNumber
Indicates the specific edition number assigned to a particular occurrence of the Olympic Games.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9506204819089dc0827483bd948 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.