Triple
T22266129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distillers Company Limited |
E550354
|
entity |
| Predicate | ownedDistillery |
P22812
|
FINISHED |
| Object | Port Ellen Distillery |
—
|
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: Port Ellen Distillery | Statement: [Distillers Company Limited, ownedDistillery, Port Ellen Distillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedDistillery Context triple: [Distillers Company Limited, ownedDistillery, Port Ellen Distillery]
-
A.
hasDistillery
chosen
Indicates that one entity owns, operates, or is associated with a distillery as a facility or production site.
-
B.
hasNearbyDistillery
Indicates that one entity is located close to or in the vicinity of a distillery.
-
C.
sisterDistillery
Indicates that two distilleries are formally associated as sister operations, typically sharing ownership, branding, or collaborative ties.
-
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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bc458c81909837373d749b915d |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:39 p.m.