Triple
T29117590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleep Train Amphitheatre |
E737088
|
entity |
| Predicate | hasFormerSponsor |
P17776
|
FINISHED |
| Object | Coors |
—
|
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: Coors | Statement: [Sleep Train Amphitheatre, hasFormerSponsor, Coors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSponsor Context triple: [Sleep Train Amphitheatre, hasFormerSponsor, Coors]
-
A.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
B.
formerSponsor
Indicates that an entity previously acted as a sponsor for another entity but no longer holds that sponsoring role.
-
C.
previousSponsorshipName
Indicates that an entity had a different sponsorship name in the past, specifying what that prior sponsored name was.
-
D.
hasSponsorSinceInauguration
Indicates that an entity has continuously had the same sponsor from the time of its inauguration or start date onward.
-
E.
previousSponsor
chosen
Indicates that an entity formerly acted as a sponsor for another entity at some earlier time but no longer does so.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 11:23 a.m.