Triple
T23478802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunnahabhain 12 Year Old |
E570343
|
entity |
| Predicate | caskMaturation |
P62362
|
FINISHED |
| Object | sherry and bourbon cask maturation |
—
|
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: sherry and bourbon cask maturation | Statement: [Bunnahabhain 12 Year Old, caskMaturation, sherry and bourbon cask maturation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caskMaturation Context triple: [Bunnahabhain 12 Year Old, caskMaturation, sherry and bourbon cask maturation]
-
A.
caskSize
Indicates the capacity or volume associated with a particular cask.
-
B.
maturesIn
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
C.
caskTypesUsed
chosen
Indicates that certain types of casks are used in relation to a given entity or process.
-
D.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
E.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74e7e648190b89006dce7d7ce05 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:02 p.m.