Triple
T18245349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meydan dirt track |
E436935
|
entity |
| Predicate | replacedAtVenue |
P101064
|
FINISHED |
| Object | Tapeta synthetic track at Meydan |
—
|
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: Tapeta synthetic track at Meydan | Statement: [Meydan dirt track, replacedAtVenue, Tapeta synthetic track at Meydan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAtVenue Context triple: [Meydan dirt track, replacedAtVenue, Tapeta synthetic track at Meydan]
-
A.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
B.
replacedVenueLocation
chosen
Indicates that one venue location has been superseded or taken over by another venue location.
-
C.
rescheduledVenue
Indicates that the location or venue for an event or activity has been changed from its original setting to a new one as part of a rescheduling.
-
D.
replacedAtPar
Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
-
E.
performedAtVenue
Indicates that an event or performance took place at a specific venue or location.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e6fbac8190bf252c4337f50c29 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.