Triple
T15692326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oban Distillery |
E380361
|
entity |
| Predicate | oneOfScotlandsOldestDistilleries |
P120303
|
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: [Oban Distillery, oneOfScotlandsOldestDistilleries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfScotlandsOldestDistilleries Context triple: [Oban Distillery, oneOfScotlandsOldestDistilleries, true]
-
A.
firstWhiskyReleased
Indicates that the subject is the entity whose first whisky was released on the specified date or in the specified release event.
-
B.
foundedAsDistillerySiteIn
Indicates that something was originally established or created as a distillery at a specific location and time.
-
C.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
-
D.
hasNearbyDistillery
Indicates that one entity is located close to or in the vicinity of a distillery.
-
E.
sisterDistillery
Indicates that two distilleries are formally associated as sister operations, typically sharing ownership, branding, or collaborative ties.
- F. None of above. chosen
Provenance (4 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:44 a.m.