Triple
T36676259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 IIHF World Championship |
E905547
|
entity |
| Predicate | finalScoreRunnerUpGoals |
P5831
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [2014 IIHF World Championship, finalScoreRunnerUpGoals, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreRunnerUpGoals Context triple: [2014 IIHF World Championship, finalScoreRunnerUpGoals, 2]
-
A.
finalScoreWinnerGoals
Indicates the number of goals scored by the winning side in the final score of a match or game.
-
B.
runnersUpGoalAverage
Indicates the average number of goals scored by entities that finished as runners-up in a competition or ranking.
-
C.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
D.
runnersUpPoints
Indicates the number of points awarded to an entity for finishing as a runner-up in a competition or ranking.
-
E.
finalScoreAway
chosen
Indicates the final score achieved by the away entity (e.g., team or participant) in a contest or event.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:12 p.m.