Triple
T18916978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force healing |
E462747
|
entity |
| Predicate | canHeal |
P83701
|
FINISHED |
| Object | physical injuries |
—
|
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: physical injuries | Statement: [Force healing, canHeal, physical injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHeal Context triple: [Force healing, canHeal, physical injuries]
-
A.
hasRemedy
chosen
Indicates that one entity serves as a remedy, treatment, or corrective measure for a problem, condition, or undesirable state associated with another entity.
-
B.
regeneratesHealthIn
Indicates that an entity’s health is restored or increased when it is within a specified context, area, or condition.
-
C.
typeOfHealing
Indicates the specific method or modality by which a healing process is carried out or achieved.
-
D.
canDie
Indicates that an entity has the capacity or possibility to die or cease living.
-
E.
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.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.