Triple
T24764518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isle of Jura warehouses |
E619542
|
entity |
| Predicate | associatedWithDistillery |
P22812
|
FINISHED |
| Object | Isle of Jura 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: Isle of Jura Distillery | Statement: [Isle of Jura warehouses, associatedWithDistillery, Isle of Jura Distillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDistillery Context triple: [Isle of Jura warehouses, associatedWithDistillery, Isle of Jura 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.
hasNearbyDistilleryBrand
Indicates that one entity has a distillery brand located in close geographic proximity to it.
-
E.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 4:28 a.m.