Triple
T18245181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Destination |
E436930
|
entity |
| Predicate | racingCareerStart |
P66169
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Dubai Destination, racingCareerStart, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingCareerStart Context triple: [Dubai Destination, racingCareerStart, 2001]
-
A.
racingDebut
Indicates the event or moment when an entity first participates in an official race or competitive racing activity.
-
B.
clubCareerStart
Indicates the point in time when an entity begins its professional or organized club-level career.
-
C.
startedRacing
chosen
Indicates that an entity began participating in a racing activity or competition, marking the initiation of its involvement in racing.
-
D.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
E.
racingNumber
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
- 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.