Triple
T23440996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caol Ila 18 Year Old |
E565401
|
entity |
| Predicate | maturationPeriod |
P32568
|
FINISHED |
| Object | 18 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: 18 years | Statement: [Caol Ila 18 Year Old, maturationPeriod, 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maturationPeriod Context triple: [Caol Ila 18 Year Old, maturationPeriod, 18 years]
-
A.
maturesIn
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
B.
maturityDuration
chosen
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
C.
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.
-
D.
firstMaturation
Indicates the point or process at which an entity undergoes its initial stage of maturation or development.
-
E.
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.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a644f6948190af07b3c4c32fc7ae |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.