Triple
T21207194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laphroaig Quarter Cask |
E522617
|
entity |
| Predicate | secondMaturation |
P143548
|
FINISHED |
| Object | quarter casks |
—
|
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: quarter casks | Statement: [Laphroaig Quarter Cask, secondMaturation, quarter casks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMaturation Context triple: [Laphroaig Quarter Cask, secondMaturation, quarter casks]
-
A.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
B.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
C.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondPhaseCompletion
Indicates that a process, project, or operation has finished its second phase or stage.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734362c788190bc1b96d3b84c0ad1 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:24 p.m.