Triple
T26704953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shona traditional religion |
E673262
|
entity |
| Predicate | explainsMisfortuneAs |
P162353
|
FINISHED |
| Object | witchcraft |
—
|
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: witchcraft | Statement: [Shona traditional religion, explainsMisfortuneAs, witchcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsMisfortuneAs Context triple: [Shona traditional religion, explainsMisfortuneAs, witchcraft]
-
A.
explainsMisfortuneAs
chosen
Indicates that one entity interprets or accounts for another entity’s misfortune as being caused or justified by a particular factor or explanation.
-
B.
explainsMoralFailureAs
Indicates that one party interprets or accounts for another party’s moral failing in terms of a particular cause, reason, or framework.
-
C.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
D.
reasonForDespair
Indicates that one entity is the cause or source of another entity’s feeling of despair.
-
E.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:33 a.m.