Triple
T22462630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Blue |
E555267
|
entity |
| Predicate | alcoholicBeverageCategory |
P14783
|
FINISHED |
| Object | whisky |
—
|
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: whisky | Statement: [Imperial Blue, alcoholicBeverageCategory, whisky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alcoholicBeverageCategory Context triple: [Imperial Blue, alcoholicBeverageCategory, whisky]
-
A.
alcoholType
chosen
Indicates the specific kind or category of alcohol associated with an entity (e.g., beer, wine, spirits).
-
B.
isAlcoholicBeverage
Indicates that a beverage contains alcohol and is classified as an alcoholic drink.
-
C.
alcoholStrengthCategory
Indicates the classification of an alcoholic beverage based on the strength or concentration of its alcohol content.
-
D.
beerStyle
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
E.
drinkFamily
Indicates a familial or close relational connection between two entities centered around drinking-related activities or contexts.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b80983081908084947b2e31c9d4 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.