Triple
T28437351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of California v. Robert Durst |
E715302
|
entity |
| Predicate | defendantDeath |
P2238
|
FINISHED |
| Object | 2022-01-10 |
—
|
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: 2022-01-10 | Statement: [State of California v. Robert Durst, defendantDeath, 2022-01-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantDeath Context triple: [State of California v. Robert Durst, defendantDeath, 2022-01-10]
-
A.
deathAfterDeposition
Indicates that one entity dies at some point after another entity has been deposed or removed from a position.
-
B.
defendant
chosen
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
C.
deathClaim
Indicates that a claim has been made asserting or reporting the death of a particular entity.
-
D.
declaredDeadInAbsentia
Indicates that an individual has been legally pronounced dead despite their physical absence or lack of a recovered body.
-
E.
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.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:43 a.m.