Triple
T34052701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antique Collection whiskeys |
E873265
|
entity |
| Predicate | whiskeyStyleIncluded |
P131858
|
FINISHED |
| Object | bourbon whiskey |
—
|
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: bourbon whiskey | Statement: [Antique Collection whiskeys, whiskeyStyleIncluded, bourbon whiskey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whiskeyStyleIncluded Context triple: [Antique Collection whiskeys, whiskeyStyleIncluded, bourbon whiskey]
-
A.
styleOfWhisky
chosen
Indicates the specific style or type category that a whisky belongs to (e.g., single malt, blended, bourbon).
-
B.
recognizesAsBestWhisky
Indicates that one entity regards another whisky as the best among a relevant set or category.
-
C.
isRyeWhiskey
Indicates that the subject is a whiskey whose primary grain in the mash bill is rye.
-
D.
isScotch
Indicates that something is identified as Scotch, specifically relating it to Scotch whisky or its origin in Scotland.
-
E.
eauxDeVieStyle
Indicates a relationship where something is characterized as being in the style or manner of eaux-de-vie (fruit brandy), typically referring to how it is produced, flavored, or presented.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.