Triple
T26341795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vincent Freeman |
E662665
|
entity |
| Predicate | predictedLifeExpectancy |
P37512
|
FINISHED |
| Object | 30.2 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: 30.2 years | Statement: [Vincent Freeman, predictedLifeExpectancy, 30.2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictedLifeExpectancy Context triple: [Vincent Freeman, predictedLifeExpectancy, 30.2 years]
-
A.
lifeExpectancyLevel
Indicates the typical or average length of life expected for an entity, often expressed as a comparative or categorical level.
-
B.
lifeExpectancyRange
Indicates the span between the minimum and maximum expected lifespan values associated with an entity.
-
C.
averageLifeExpectancyRank
Indicates the relative position of an entity in a ranking ordered by average life expectancy, typically compared to other entities in the same set or population.
-
D.
lifeExpectancyRank
Indicates the relative position of an entity in an ordered list based on its life expectancy compared to others.
-
E.
deathAge
chosen
Indicates the age at which an entity dies or is expected to die.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:39 p.m.