Triple
T35330338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldora Speedway |
E1020298
|
entity |
| Predicate | sanctioningBodyEventHosted |
P183021
|
FINISHED |
| Object | World of Outlaws Sprint Car 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: World of Outlaws Sprint Car Series | Statement: [Eldora Speedway, sanctioningBodyEventHosted, World of Outlaws Sprint Car Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningBodyEventHosted Context triple: [Eldora Speedway, sanctioningBodyEventHosted, World of Outlaws Sprint Car Series]
-
A.
countryHostedEvent
Indicates that a specific country served as the host location for a particular event.
-
B.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
-
C.
secretariatHostedBy
Indicates that a particular secretariat is accommodated, organized, or institutionally supported by a specified host entity.
-
D.
hasEventHostingCapability
Indicates that an entity possesses the ability or resources to host or organize events.
-
E.
sanctioningOrganization
Indicates the organization that formally imposes, authorizes, or enforces a sanction on another party.
- F. None of above. chosen
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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.