Triple
T10570454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo Trace Distillery |
E249463
|
entity |
| Predicate | usesMashBill |
P94218
|
FINISHED |
| Object | corn-based bourbon mash bills |
—
|
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: corn-based bourbon mash bills | Statement: [Buffalo Trace Distillery, usesMashBill, corn-based bourbon mash bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMashBill Context triple: [Buffalo Trace Distillery, usesMashBill, corn-based bourbon mash bills]
-
A.
hasMashBill
chosen
Indicates that an alcoholic beverage (typically a spirit like whiskey or bourbon) is produced using a specific mixture of grains (the mash bill).
-
B.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
C.
typeOfMalt
Indicates the specific kind or category of malt used or referenced in relation to another entity.
-
D.
isMixedBeer
Indicates that a beer is composed by mixing two or more different beers together.
-
E.
typicalOriginalGravity
Indicates the usual or characteristic original gravity value associated with a given beer style or recipe.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5274678148190b7a1afc099628357 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.