Triple
T5755198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR Xfinity Series |
E126947
|
entity |
| Predicate | titleSponsorSince |
P24881
|
FINISHED |
| Object | 2015 |
—
|
LITERAL 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: 2015 | Statement: [NASCAR Xfinity Series, titleSponsorSince, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleSponsorSince Context triple: [NASCAR Xfinity Series, titleSponsorSince, 2015]
-
A.
sponsorshipNameSince
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
B.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
C.
hasTitleSponsor
chosen
Indicates that one entity serves as the primary (title) sponsor for another entity, typically giving its name to the sponsored event, organization, or property.
-
D.
hasTitleSponsorHistorically
Indicates that an entity has served as the primary (title) sponsor of another entity during some period in the past.
-
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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02904dcf481909e4340a64ee1034e |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.