Triple
T13590803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom Pérignon |
E324686
|
entity |
| Predicate | typicalAgingOnLees |
P53135
|
FINISHED |
| Object | at least 7 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: at least 7 years | Statement: [Dom Pérignon, typicalAgingOnLees, at least 7 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgingOnLees Context triple: [Dom Pérignon, typicalAgingOnLees, at least 7 years]
-
A.
typicalAgingTime
chosen
Indicates the usual duration required for something to age or mature under normal conditions.
-
B.
typicalAgingPotentialRange
Indicates the usual range of time over which something is expected to age or mature under normal conditions.
-
C.
turnedSenior
Indicates that an entity has transitioned into senior status or a senior role relative to a previous state or position.
-
D.
laterLifePractice
Indicates that an individual engaged in a particular activity, role, or practice during the later period of their life.
-
E.
mayBeAgedIn
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.