Triple
T38542019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Shandy |
E924856
|
entity |
| Predicate | isFlagshipSeasonalFor |
P191180
|
FINISHED |
| Object | Leinenkugel’s |
—
|
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: Leinenkugel’s | Statement: [Summer Shandy, isFlagshipSeasonalFor, Leinenkugel’s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlagshipSeasonalFor Context triple: [Summer Shandy, isFlagshipSeasonalFor, Leinenkugel’s]
-
A.
hasSeasonalCollections
Indicates that an entity offers or maintains collections that vary according to specific seasons or times of year.
-
B.
isSeasonalRelease
Indicates that something is released only during a specific season or limited time period tied to the calendar.
-
C.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
D.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
E.
hasSeasonalOffering
Indicates that an entity provides or features a special offering that is available only during a particular season or time of year.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.