Triple
T35330546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NASCAR Busch Series |
E1020303
|
entity |
| Predicate | openingRaceTrack |
P124147
|
FINISHED |
| Object | Daytona International Speedway |
—
|
NE NERFINISHED |
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 International Speedway | Statement: [1991 NASCAR Busch Series, openingRaceTrack, Daytona International Speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingRaceTrack Context triple: [1991 NASCAR Busch Series, openingRaceTrack, Daytona International Speedway]
-
A.
racecourseOpened
Indicates that a racecourse began operating or was officially opened on a specified date or at a specified time.
-
B.
raceTrack
chosen
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
C.
openingRace
Indicates that one race serves as the initial or first event in a sequence of races or a racing competition.
-
D.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
E.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:03 p.m.