Triple
T6708754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbaresco |
E153074
|
entity |
| Predicate | typicalAgingPotentialRange |
P72565
|
FINISHED |
| Object | 10–20 years or more |
—
|
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: 10–20 years or more | Statement: [Barbaresco, typicalAgingPotentialRange, 10–20 years or more]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgingPotentialRange Context triple: [Barbaresco, typicalAgingPotentialRange, 10–20 years or more]
-
A.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
-
D.
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.
-
E.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.