Triple
T23070094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunnahabhain 25 Year Old |
E575167
|
entity |
| Predicate | parentDistillery |
P22812
|
FINISHED |
| Object | Bunnahabhain |
—
|
NE NERFINISHED |
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: Bunnahabhain | Statement: [Bunnahabhain 25 Year Old, parentDistillery, Bunnahabhain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentDistillery Context triple: [Bunnahabhain 25 Year Old, parentDistillery, Bunnahabhain]
-
A.
sisterDistillery
Indicates that two distilleries are formally associated as sister operations, typically sharing ownership, branding, or collaborative ties.
-
B.
hasDistillery
chosen
Indicates that one entity owns, operates, or is associated with a distillery as a facility or production site.
-
C.
hasNearbyDistillery
Indicates that one entity is located close to or in the vicinity of a distillery.
-
D.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
-
E.
hasNearbyDistilleryBrand
Indicates that one entity has a distillery brand located in close geographic proximity to 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c5f17348190ab92cfdae9bcaeba |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:56 p.m.