Triple
T36468268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Simpson |
E898475
|
entity |
| Predicate | hasApproximateAgeAtDeath |
P28983
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Thomas Simpson, hasApproximateAgeAtDeath, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateAgeAtDeath Context triple: [Thomas Simpson, hasApproximateAgeAtDeath, 50]
-
A.
approximateAgeAtDeath
chosen
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
-
B.
diedInAge
Indicates that an entity died at a specified age.
-
C.
estimatedDateOfDeath
Indicates the date on which an entity is believed or calculated to have died, rather than a precisely known death date.
-
D.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
E.
livedApproximately
Indicates that an entity’s lifespan or period of residence is known only roughly, with approximate rather than exact dates.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.