Triple
T23257741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Paul Koroma |
E581916
|
entity |
| Predicate | wasDeclaredDeadInAbsentia |
P126662
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Johnny Paul Koroma, wasDeclaredDeadInAbsentia, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDeclaredDeadInAbsentia Context triple: [Johnny Paul Koroma, wasDeclaredDeadInAbsentia, 2003]
-
A.
declaredDeadInAbsentia
chosen
Indicates that an individual has been legally pronounced dead despite their physical absence or lack of a recovered body.
-
B.
evidenceForImpliedDeath
Indicates that something serves as supporting evidence for the conclusion that a death has occurred, even if the death itself is not directly observed or explicitly stated.
-
C.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
D.
deathClaim
Indicates that a claim has been made asserting or reporting the death of a particular entity.
-
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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c5f5bc8190ac8776f7f7430209 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.