Triple
T33670293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cole Trickle |
E862598
|
entity |
| Predicate | notableRaceSeriesInFilm |
P206624
|
FINISHED |
| Object | Daytona 500 |
E87857
|
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: Daytona 500 | Statement: [Cole Trickle, notableRaceSeriesInFilm, Daytona 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaceSeriesInFilm Context triple: [Cole Trickle, notableRaceSeriesInFilm, Daytona 500]
-
A.
notableRaceTrackDepicted
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
B.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
-
C.
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.
-
D.
racedInSeries
Indicates that an entity participated as a competitor in a particular racing series or championship.
-
E.
notablePerformanceSeries
Indicates a recurring set of performances or appearances by an entity that are recognized as particularly significant or noteworthy.
- F. None of above. chosen
Provenance (5 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36272e840c8190b2fc0c0ba5f8ea3b |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.