Triple
T14107264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guna traditional religion |
E339537
|
entity |
| Predicate | viewOnIllness |
P112834
|
FINISHED |
| Object | illness can be caused by spiritual imbalance |
—
|
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: illness can be caused by spiritual imbalance | Statement: [Guna traditional religion, viewOnIllness, illness can be caused by spiritual imbalance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnIllness Context triple: [Guna traditional religion, viewOnIllness, illness can be caused by spiritual imbalance]
-
A.
viewOnPain
Indicates a stance, belief, or perspective that an entity holds regarding the nature, causes, or significance of pain.
-
B.
viewOnHealing
Indicates a stance, belief, or perspective that an entity holds regarding the nature, process, or principles of healing.
-
C.
viewOnLife
Indicates a person's general attitude, perspective, or philosophy regarding life.
-
D.
illness
Indicates that an entity is affected by, or suffering from, a particular disease or medical condition.
-
E.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.