Triple
T22144017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | !Kung people |
E547237
|
entity |
| Predicate | healingPractice |
P130966
|
FINISHED |
| Object | trance healing |
—
|
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: trance healing | Statement: [!Kung people, healingPractice, trance healing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healingPractice Context triple: [!Kung people, healingPractice, trance healing]
-
A.
typeOfHealing
chosen
Indicates the specific method or modality by which a healing process is carried out or achieved.
-
B.
sacramentOfHealing
Indicates a relationship in which a religious sacrament is administered to bring spiritual or physical healing to a person.
-
C.
cultPractices
Indicates involvement in or performance of rituals, beliefs, or behaviors associated with a cult.
-
D.
practicedMedicineOfTradition
Indicates that an entity engaged in the medical practices or healing methods associated with a particular cultural or traditional system.
-
E.
ritualTreatment
Indicates a relationship where an entity performs or undergoes a ritualized act or procedure intended to affect, purify, protect, or transform another entity or condition.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129c045448190b3d189cdb8c0d2fd |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.