Triple
T20887184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 IIHF World Championship |
E514312
|
entity |
| Predicate | openingGameAttendanceRecord |
P26094
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2010 IIHF World Championship, openingGameAttendanceRecord, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingGameAttendanceRecord Context triple: [2010 IIHF World Championship, openingGameAttendanceRecord, yes]
-
A.
fanAttendance
chosen
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
B.
openingMatchScore
Indicates the degree of similarity or compatibility between an opening (e.g., a position, role, or opportunity) and a given candidate or item, typically expressed as a numeric score.
-
C.
stadiumOpeningForGames
Indicates that a stadium is being opened or made available specifically for hosting games or sporting events.
-
D.
SuperBowlAttendance
Indicates the number of people who attended a given Super Bowl event.
-
E.
openedWithStadium
Indicates that something (such as an event, season, or facility) began or was inaugurated concurrently with the opening of a particular stadium.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d058d4dc81908398f8c75e30dc77 |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.