Triple
T26704936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shona traditional religion |
E673262
|
entity |
| Predicate | nangaDefinedAs |
P773
|
FINISHED |
| Object | traditional healer |
—
|
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: traditional healer | Statement: [Shona traditional religion, nangaDefinedAs, traditional healer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nangaDefinedAs Context triple: [Shona traditional religion, nangaDefinedAs, traditional healer]
-
A.
normDefinedBy
Indicates that a norm, rule, or standard is established, specified, or determined by a particular source or authority.
-
B.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
D.
ånMeans
Indicates that one entity serves as the meaning, definition, or semantic equivalent of another entity.
-
E.
mathematicallyDefinedAs
Indicates that one entity is precisely specified or characterized in terms of another using a formal mathematical definition or expression.
- 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_69f617b8e61881909eef2e8eaf1bc969 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:33 a.m.