Triple
T5644925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagavulin distillery |
E124360
|
entity |
| Predicate | hasMaturationLocation |
P65393
|
FINISHED |
| Object | Islay warehouses |
—
|
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: Islay warehouses | Statement: [Lagavulin distillery, hasMaturationLocation, Islay warehouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaturationLocation Context triple: [Lagavulin distillery, hasMaturationLocation, Islay warehouses]
-
A.
hasStageLocation
Indicates that an event, process, or staged activity occurs at or is associated with a specific location.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
D.
hasPrimaryAssetLocation
Indicates that an entity’s main or principal asset is located at a specified place or facility.
-
E.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a8eccc8190837d4705670dc25e |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.