Triple
T22524650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islay single malt |
E556867
|
entity |
| Predicate | agingLocationRequirement |
P43060
|
FINISHED |
| Object | oak casks in Scotland |
—
|
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: oak casks in Scotland | Statement: [Islay single malt, agingLocationRequirement, oak casks in Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingLocationRequirement Context triple: [Islay single malt, agingLocationRequirement, oak casks in Scotland]
-
A.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
B.
locationRequirement
chosen
Indicates that a specific location or type of place is required or must be satisfied for an action, condition, or relationship to hold.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
membershipLocation
Indicates that an entity’s membership or affiliation is associated with, based in, or held at a particular location.
-
E.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e356b4081909d1ce911bd35fe68 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:51 p.m.