Triple
T24384312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover International Speedway |
E614700
|
entity |
| Predicate | formerSeriesHosted |
P113978
|
FINISHED |
| Object | IndyCar Series |
—
|
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: IndyCar Series | Statement: [Dover International Speedway, formerSeriesHosted, IndyCar Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSeriesHosted Context triple: [Dover International Speedway, formerSeriesHosted, IndyCar Series]
-
A.
formerHostsSeries
chosen
Indicates that an entity previously hosted, but no longer hosts, a particular series.
-
B.
formerSeries
Indicates that one entity was previously a series associated with another entity, but no longer holds that status.
-
C.
hostsSeries
Indicates that an entity regularly presents, moderates, or leads a particular series (such as a show, event, or program).
-
D.
primarySeriesHosted
Indicates that an entity serves as the main host or venue for a particular series or recurring event.
-
E.
formerCoHostOf
Indicates that one entity previously served as a co-host together with another entity, but no longer holds that co-hosting role.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294533b3881908c228a021c254006 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.