Triple
T28004457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Chris Hoy Velodrome |
E707237
|
entity |
| Predicate | keyVenueFor |
P5921
|
FINISHED |
| Object | 2014 Commonwealth Games |
—
|
NE NERFINISHED |
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: 2014 Commonwealth Games | Statement: [Sir Chris Hoy Velodrome, keyVenueFor, 2014 Commonwealth Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyVenueFor Context triple: [Sir Chris Hoy Velodrome, keyVenueFor, 2014 Commonwealth Games]
-
A.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
-
B.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
C.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
D.
primaryVenueFor
chosen
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
E.
notableVenueFor
Indicates that a venue is especially recognized or significant for hosting, presenting, or being associated with a particular entity or activity.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd4e25c81909b4a26577a4a5479 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:59 p.m.