Triple
T14833508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hockey Stadium |
E348767
|
entity |
| Predicate | wasCompetitionVenueFor |
P21366
|
FINISHED |
| Object | 2008 Summer Olympics |
—
|
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: 2008 Summer Olympics | Statement: [National Hockey Stadium, wasCompetitionVenueFor, 2008 Summer Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCompetitionVenueFor Context triple: [National Hockey Stadium, wasCompetitionVenueFor, 2008 Summer Olympics]
-
A.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
B.
locationOfCompetition
chosen
Indicates the place or venue where a competition or contest takes or took place.
-
C.
significantVenueFor
Indicates that a venue plays an important or notable role in relation to a particular entity, event, or activity.
-
D.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
E.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.