Triple
T11069493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labatt Brewing Company |
E261706
|
entity |
| Predicate | notableBeerStyle |
P52234
|
FINISHED |
| Object | Canadian lager |
—
|
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: Canadian lager | Statement: [Labatt Brewing Company, notableBeerStyle, Canadian lager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBeerStyle Context triple: [Labatt Brewing Company, notableBeerStyle, Canadian lager]
-
A.
beerStyle
chosen
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
B.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
C.
beerStyleOrigin
Indicates the place or region where a particular beer style was originally developed or first became established.
-
D.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
E.
notableBrewmaster
Indicates that an entity is recognized for being an outstanding or distinguished brewmaster, typically noted for significant skill, influence, or achievement in brewing.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799221e848190b0f86ae3eb5e3e02 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.