Triple
T17187976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richey Edwards |
E417155
|
entity |
| Predicate | declaredDeadInAbsentia |
P126662
|
FINISHED |
| Object | 2008-11 |
—
|
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: 2008-11 | Statement: [Richey Edwards, declaredDeadInAbsentia, 2008-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredDeadInAbsentia Context triple: [Richey Edwards, declaredDeadInAbsentia, 2008-11]
-
A.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
B.
deathAnnouncedBy
Indicates that the occurrence of a death is publicly communicated or formally reported by a specific agent or source.
-
C.
possiblyDiedIn
Indicates that an entity is believed or suspected to have died in a particular place, but this is uncertain or not definitively confirmed.
-
D.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
E.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
- F. None of above. chosen
Provenance (4 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d97b9808190aa1900775cd3dfd5 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.