Triple
T6028770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilchoman distillery |
E134245
|
entity |
| Predicate | usesBarleySource |
P46735
|
FINISHED |
| Object | Islay-grown barley |
—
|
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: Islay-grown barley | Statement: [Kilchoman distillery, usesBarleySource, Islay-grown barley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBarleySource Context triple: [Kilchoman distillery, usesBarleySource, Islay-grown barley]
-
A.
hasSourceMaterial
chosen
Indicates that something is derived from, based on, or created using a particular source material.
-
B.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
C.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
D.
isMixedBeer
Indicates that a beer is composed by mixing two or more different beers together.
-
E.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified entity.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560fdc84819093abba13054ea1ee |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.