Triple
T6131609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobermory Distillery |
E136730
|
entity |
| Predicate | usesBarleyType |
P32631
|
FINISHED |
| Object | Scottish malted 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: Scottish malted barley | Statement: [Tobermory Distillery, usesBarleyType, Scottish malted barley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBarleyType Context triple: [Tobermory Distillery, usesBarleyType, Scottish malted barley]
-
A.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
B.
yeastType
Indicates the specific kind or category of yeast associated with or used in relation to an entity.
-
C.
hasGrainType
chosen
Indicates that an entity is characterized by or associated with a specific type of grain.
-
D.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
E.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4f7ad8819096b09ddd312453fb |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.