Triple
T4315714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Millennium |
E96385
|
entity |
| Predicate | racingRecord |
P51153
|
FINISHED |
| Object | 10 starts, 9 wins, 0 seconds, 0 thirds |
—
|
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: 10 starts, 9 wins, 0 seconds, 0 thirds | Statement: [Dubai Millennium, racingRecord, 10 starts, 9 wins, 0 seconds, 0 thirds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingRecord Context triple: [Dubai Millennium, racingRecord, 10 starts, 9 wins, 0 seconds, 0 thirds]
-
A.
raceWins
Indicates that one participant wins or finishes ahead of another in a race or competitive event.
-
B.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
C.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
D.
raceStatus
Indicates the current state or progress of an entity’s participation in a race or competitive event.
-
E.
racesEntered
chosen
Indicates that an entity has participated in or registered for one or more races.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350f60dfc819098202b7eb3bbf402 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.