Triple
T21289685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laphroaig 10 Year Old Cask Strength |
E524752
|
entity |
| Predicate | chillFiltered |
P141255
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Laphroaig 10 Year Old Cask Strength, chillFiltered, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chillFiltered Context triple: [Laphroaig 10 Year Old Cask Strength, chillFiltered, no]
-
A.
nonChillFiltered
chosen
Indicates that a beverage, typically a spirit, has not undergone chill filtration to remove particles or compounds before bottling.
-
B.
filter
Indicates that one entity selectively includes or excludes elements of another entity based on specified criteria or conditions.
-
C.
usesFilter
Indicates that one entity applies or employs a filter (such as a criterion, condition, or processing mechanism) to another entity or set of data.
-
D.
cutOff
Indicates that one entity causes another entity to be disconnected, interrupted, or severed from a source, flow, or continuation.
-
E.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d9467881908ec5b1dec76e6f5d |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.