Triple
T25648828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solan Lochs |
E643041
|
entity |
| Predicate | belongsToWhiskyRegion |
P81068
|
FINISHED |
| Object | Islay whisky region |
—
|
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: Islay whisky region | Statement: [Solan Lochs, belongsToWhiskyRegion, Islay whisky region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWhiskyRegion Context triple: [Solan Lochs, belongsToWhiskyRegion, Islay whisky region]
-
A.
whiskyRegionOf
chosen
Indicates the geographical region where a particular whisky is produced or originates.
-
B.
hasWhiskyRegionStatus
Indicates that an entity holds an official or recognized status as a whisky-producing region.
-
C.
includesDistilleryRegion
Indicates that one entity encompasses or contains the geographic region associated with a particular distillery.
-
D.
beerStyleRegion
Indicates the geographic region or origin associated with a particular beer style.
-
E.
isInWineOrSpiritsRegion
Indicates that one entity (typically a location or product) is situated within or associated with a designated wine or spirits-producing region of another entity.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 6:16 p.m.