Triple
T22548282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burn Stewart Distillers |
E557487
|
entity |
| Predicate | operatesDistillery |
P22812
|
FINISHED |
| Object | Deanston 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: Deanston Distillery | Statement: [Burn Stewart Distillers, operatesDistillery, Deanston Distillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDistillery Context triple: [Burn Stewart Distillers, operatesDistillery, Deanston 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.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
-
D.
hasApproximateNumberOfDistilleries
Indicates that an entity is associated with an estimated or approximate count of distilleries.
-
E.
distillationType
Indicates the specific method or process of distillation used to separate or refine substances.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f372df48190ae5dd461b1230bc7 |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.