Triple
T30152764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Creed |
E766436
|
entity |
| Predicate | caredForCondition |
P28603
|
FINISHED |
| Object | 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: terminal illness | Statement: [Rachel Creed, caredForCondition, terminal illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caredForCondition Context triple: [Rachel Creed, caredForCondition, terminal illness]
-
A.
sufferedCondition
Indicates that an entity experienced or was afflicted by a particular condition, typically adverse or harmful, at some point in time.
-
B.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
C.
tookCareOf
chosen
Indicates that one entity provided care, support, or maintenance for another entity over a period of time.
-
D.
conditionForSparing
Indicates that one entity specifies the circumstances under which another entity is exempted from harm, penalty, or adverse action.
-
E.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4df5081908d1431e3a1a1fb0e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.