Triple
T24729142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Stadium, Vancouver |
E618234
|
entity |
| Predicate | notableRaceDate |
P167702
|
FINISHED |
| Object | 1954-08-07 |
—
|
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: 1954-08-07 | Statement: [Empire Stadium, Vancouver, notableRaceDate, 1954-08-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaceDate Context triple: [Empire Stadium, Vancouver, notableRaceDate, 1954-08-07]
-
A.
notableRaceMeeting
Indicates that there is a race meeting or event that is particularly notable or significant in relation to the subject.
-
B.
notableRaceNumber
Indicates that a specific race is distinguished as notable for an entity, typically by assigning it a particular identifying number.
-
C.
notableRaceStatus
Indicates that an entity holds a distinguished or significant status in the context of a particular race or racing event.
-
D.
notableRacingSuccess
Indicates that the subject has achieved significant or distinguished success in competitive racing events.
-
E.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 18, 2026, 4:01 a.m.