Triple
T4412948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meydan grandstand complex |
E94892
|
entity |
| Predicate | openedForRacingAtMeydan |
P16266
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Meydan grandstand complex, openedForRacingAtMeydan, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForRacingAtMeydan Context triple: [Meydan grandstand complex, openedForRacingAtMeydan, 2010]
-
A.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
B.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
C.
hasRacecourse
chosen
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
raceStartType
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
E.
frontRunnerAtStart
Indicates that an entity is the leading competitor or in first position at the beginning of an event or process.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e7b30c819082ee781dd202dcc4 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.