Triple
T34508358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim McDowell |
E885948
|
entity |
| Predicate | patientSurvived |
P53287
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ephraim McDowell, patientSurvived, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patientSurvived Context triple: [Ephraim McDowell, patientSurvived, yes]
-
A.
survivedDisease
Indicates that an entity successfully lived through and recovered from a specified disease.
-
B.
hasSurvivalStatus
chosen
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
-
C.
survivedAccident
Indicates that an entity continued to live or remain unharmed after being involved in an accident.
-
D.
survivalAttributedTo
Indicates that an entity’s continued existence or survival is credited to, or causally linked with, another entity or factor.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.