Triple
T28946248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temiar |
E730587
|
entity |
| Predicate | healingSystem |
P130966
|
FINISHED |
| Object | shamanic curing |
—
|
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: shamanic curing | Statement: [Temiar, healingSystem, shamanic curing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healingSystem Context triple: [Temiar, healingSystem, shamanic curing]
-
A.
regeneratesHealthIn
Indicates that an entity’s health is restored or increased when it is within a specified context, area, or condition.
-
B.
healthPointsJava
Indicates the number of health points an entity has within a Java-based context or implementation.
-
C.
typeOfHealing
chosen
Indicates the specific method or modality by which a healing process is carried out or achieved.
-
D.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65b8710908190b3746b9a711484b3 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:40 a.m.