Triple
T32193057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Foster |
E822315
|
entity |
| Predicate | isDyingFrom |
P89293
|
FINISHED |
| Object | unspecified terminal illness |
—
|
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: unspecified terminal illness | Statement: [Jason Foster, isDyingFrom, unspecified terminal illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDyingFrom Context triple: [Jason Foster, isDyingFrom, unspecified terminal illness]
-
A.
diesBy
Indicates that one entity causes or is responsible for the death of another entity.
-
B.
canDieIn
Indicates that one entity is capable of dying, ceasing to exist, or being destroyed within, because of, or in the context of another entity or situation.
-
C.
deathIs
chosen
Indicates that one entity is the cause, manner, or circumstance of another entity’s death.
-
D.
canDie
Indicates that an entity has the capacity or possibility to die or cease living.
-
E.
nearlyDiesFrom
Indicates that an entity comes very close to dying as a result of another entity or event, but ultimately survives.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb35369c8190992fe7dad36a2a9d |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.