Triple
T37850541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leinenkugel’s Session Helles |
E944040
|
entity |
| Predicate | originBreweryState |
P66978
|
FINISHED |
| Object | Wisconsin |
E16627
|
NE 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: Wisconsin | Statement: [Leinenkugel’s Session Helles, originBreweryState, Wisconsin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originBreweryState Context triple: [Leinenkugel’s Session Helles, originBreweryState, Wisconsin]
-
A.
breweryFoundedIn
Indicates that a brewery was established or began operating in a specific year or time period.
-
B.
beerBrandOrigin
Indicates the place or country where a particular beer brand was originally created or first produced.
-
C.
bottledBy
Indicates that one entity is responsible for placing another entity into bottles or containers for packaging or distribution.
-
D.
knownBrewer
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
-
E.
breweryLocation
chosen
Indicates the place where a brewery is situated or operates.
- F. None of above.
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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4104164c188190a01e59c02124345c |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.