Triple
T23676606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothes |
E584893
|
entity |
| Predicate | locatedInWhiskyRegion |
P81068
|
FINISHED |
| Object | Speyside 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: Speyside whisky region | Statement: [Rothes, locatedInWhiskyRegion, Speyside whisky region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInWhiskyRegion Context triple: [Rothes, locatedInWhiskyRegion, Speyside whisky region]
-
A.
whiskyRegionOf
chosen
Indicates the geographical region where a particular whisky is produced or originates.
-
B.
includesDistilleryRegion
Indicates that one entity encompasses or contains the geographic region associated with a particular distillery.
-
C.
hasWhiskyRegionStatus
Indicates that an entity holds an official or recognized status as a whisky-producing region.
-
D.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
-
E.
wineClassificationRegion
Indicates that a wine is classified according to the geographic region where it is produced or designated.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f40c9081908ef0cddb6f0392da |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.