Triple
T9130633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor Tree |
E219075
|
entity |
| Predicate | nursedBackToHealth |
P28603
|
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: [Survivor Tree, nursedBackToHealth, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nursedBackToHealth Context triple: [Survivor Tree, nursedBackToHealth, yes]
-
A.
recoveredWithAidFrom
Indicates that an entity returned to a prior or improved state (such as health, function, or condition) as a result of assistance, intervention, or support from another entity.
-
B.
tookCareOf
chosen
Indicates that one entity provided care, support, or maintenance for another entity over a period of time.
-
C.
curedWith
Indicates that one entity is treated or healed by using another entity as the remedy or therapeutic method.
-
D.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
-
E.
viewOnHealing
Indicates a stance, belief, or perspective that an entity holds regarding the nature, process, or principles of healing.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cdafb48190be5e62b15779d771 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.