Triple
T13563407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Véran |
E323968
|
entity |
| Predicate | typicalMaturationPotential |
P86480
|
FINISHED |
| Object | 3–5 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–5 years | Statement: [Saint-Véran, typicalMaturationPotential, 3–5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaturationPotential Context triple: [Saint-Véran, typicalMaturationPotential, 3–5 years]
-
A.
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.
-
B.
maturesIn
chosen
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
C.
maturesLateComparedTo
Indicates that one entity reaches maturity significantly later in time than another entity used as a reference.
-
D.
maturity
Indicates that an entity has reached a specified stage of development, completeness, or readiness, often marking the point at which certain rights, obligations, or behaviors become applicable.
-
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.
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.