Triple
T35564271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Meijer 300 at Kentucky Speedway |
E1027724
|
entity |
| Predicate | presentingSponsor |
P35686
|
FINISHED |
| Object | Oreo |
—
|
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: Oreo | Statement: [2008 Meijer 300 at Kentucky Speedway, presentingSponsor, Oreo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentingSponsor Context triple: [2008 Meijer 300 at Kentucky Speedway, presentingSponsor, Oreo]
-
A.
coSponsor
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
B.
hasSponsor
chosen
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
C.
previousSponsor
Indicates that an entity formerly acted as a sponsor for another entity at some earlier time but no longer does so.
-
D.
prizeSponsor
Indicates that an entity provides financial or material support as the sponsor of a particular prize or award.
-
E.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:04 p.m.