Triple
T30948753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishbi-Erra of Isin |
E788473
|
entity |
| Predicate | approximateDeath |
P28122
|
FINISHED |
| Object | late 20th century BCE |
—
|
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: late 20th century BCE | Statement: [Ishbi-Erra of Isin, approximateDeath, late 20th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDeath Context triple: [Ishbi-Erra of Isin, approximateDeath, late 20th century BCE]
-
A.
deathApprox
chosen
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
B.
estimatedDateOfDeath
Indicates the date on which an entity is believed or calculated to have died, rather than a precisely known death date.
-
C.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
-
D.
nearlyDiesFrom
Indicates that an entity comes very close to dying as a result of another entity or event, but ultimately survives.
-
E.
possiblyDiedIn
Indicates that an entity is believed or suspected to have died in a particular place, but this is uncertain or not definitively confirmed.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:53 p.m.