Triple
T23217442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talisker distillery |
E580787
|
entity |
| Predicate | usesPeatedMalt |
P69348
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Talisker distillery, usesPeatedMalt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPeatedMalt Context triple: [Talisker distillery, usesPeatedMalt, true]
-
A.
isPeated
Indicates that something has been treated with or characterized by peat, typically imparting a smoky or earthy quality.
-
B.
hasPeatingLevelRange
Indicates that something is associated with a specified range of peatiness levels, typically expressing how peated or smoky it is within defined minimum and maximum bounds.
-
C.
typeOfMalt
chosen
Indicates the specific kind or category of malt used or referenced in relation to another entity.
-
D.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
-
E.
recognizesAsBestWhisky
Indicates that one entity regards another whisky as the best among a relevant set or category.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916653f08190a7dcbc659c6b6a25 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.