Triple
T6523310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barolo |
E151240
|
entity |
| Predicate | riservaMinimumAgingRequirement |
P71398
|
FINISHED |
| Object | 62 months |
—
|
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: 62 months | Statement: [Barolo, riservaMinimumAgingRequirement, 62 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riservaMinimumAgingRequirement Context triple: [Barolo, riservaMinimumAgingRequirement, 62 months]
-
A.
wineAgeingPotential
Indicates the capacity or suitability of a wine to improve in quality or maintain desirable characteristics over time with proper aging.
-
B.
vineAge
Indicates the age or length of time that a vine has been growing or established.
-
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.
wineAgeingPreference
Indicates a preference for how long wine should be aged before consumption or use.
-
E.
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.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad970afc81909d3231203eacf413 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:45 p.m.