Triple
T18911560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop-Tarts Bowl |
E462619
|
entity |
| Predicate | hasTitleSponsorSince |
P40278
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Pop-Tarts Bowl, hasTitleSponsorSince, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleSponsorSince Context triple: [Pop-Tarts Bowl, hasTitleSponsorSince, 2023]
-
A.
hasTitleSponsor
Indicates that one entity serves as the primary (title) sponsor for another entity, typically giving its name to the sponsored event, organization, or property.
-
B.
hasTitleSponsorHistorically
Indicates that an entity has served as the primary (title) sponsor of another entity during some period in the past.
-
C.
sponsorshipNameSince
chosen
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
D.
hasSponsorSinceInauguration
Indicates that an entity has continuously had the same sponsor from the time of its inauguration or start date onward.
-
E.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c6238e288190b30311b5d80beafb |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.