Triple
T33422266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dust to Glory |
E855874
|
entity |
| Predicate | notableRaceCovered |
P118371
|
FINISHED |
| Object | 2003 Baja 1000 |
E2048823
|
NE 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: 2003 Baja 1000 | Statement: [Dust to Glory, notableRaceCovered, 2003 Baja 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaceCovered Context triple: [Dust to Glory, notableRaceCovered, 2003 Baja 1000]
-
A.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
-
B.
notableRaceMeeting
Indicates that there is a race meeting or event that is particularly notable or significant in relation to the subject.
-
C.
notableRaceDate
Indicates that a specific date is recognized as significant or noteworthy for a particular race event.
-
D.
notableRaceTrackDepicted
chosen
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
E.
notableRacingSuccess
Indicates that the subject has achieved significant or distinguished success in competitive racing events.
- F. None of above.
Provenance (4 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afbdf2e08190b8ac4ee93c699859 |
completed | June 19, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.