Triple
T22101801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lease of Life |
E546188
|
entity |
| Predicate | hasTerminalIllnessPlot |
P105753
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lease of Life, hasTerminalIllnessPlot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalIllnessPlot Context triple: [Lease of Life, hasTerminalIllnessPlot, true]
-
A.
isTerminallyIll
Indicates that an entity is suffering from an incurable illness expected to lead to death in the relatively near future.
-
B.
hasPlot
chosen
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
C.
hasPrognosis
Indicates that one entity (typically a medical condition or case) is associated with an expected course or outcome over time, such as likely progression, duration, or chances of recovery.
-
D.
legalStatusAtEndOfLife
Indicates the legal classification or condition that applies to an entity at the time of its termination, dissolution, or death.
-
E.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129163b908190b63ace06016f4db8 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.