Triple
T4087115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotch whisky |
E87613
|
entity |
| Predicate | minimumMaturationPeriod |
P32568
|
FINISHED |
| Object | 3 years |
—
|
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: 3 years | Statement: [Scotch whisky, minimumMaturationPeriod, 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumMaturationPeriod Context triple: [Scotch whisky, minimumMaturationPeriod, 3 years]
-
A.
maturityDuration
chosen
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
B.
maturityRange
Indicates the span or limits of maturity (such as age, development stage, or readiness) within which the related entities or conditions are considered applicable.
-
C.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
-
D.
maximumBondMaturity
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
-
E.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7ceeb48190807f0f5078ccfa12 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.