Triple
T7528405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europeans |
E177952
|
entity |
| Predicate | hasAverageLifeExpectancy |
P12164
|
FINISHED |
| Object | relatively high |
—
|
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: relatively high | Statement: [Europeans, hasAverageLifeExpectancy, relatively high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageLifeExpectancy Context triple: [Europeans, hasAverageLifeExpectancy, relatively high]
-
A.
lifeExpectancyLevel
chosen
Indicates the typical or average length of life expected for an entity, often expressed as a comparative or categorical level.
-
B.
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.
-
C.
deathAge
Indicates the age at which an entity dies or is expected to die.
-
D.
lifeExpectancyRank
Indicates the relative position of an entity in an ordered list based on its life expectancy compared to others.
-
E.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81e19208190965f211d057f7fdf |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.