Triple
T26351026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himba |
E662900
|
entity |
| Predicate | cosmologyDeity |
P161283
|
FINISHED |
| Object | Mukuru |
—
|
NE NERFINISHED |
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: Mukuru | Statement: [Himba, cosmologyDeity, Mukuru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmologyDeity Context triple: [Himba, cosmologyDeity, Mukuru]
-
A.
cosmologicalDoctrine
Indicates a relationship where an entity articulates, endorses, or is characterized by a systematic set of beliefs or theories about the origin, structure, and fundamental nature of the cosmos.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
-
D.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
E.
deityDomain
Indicates that a deity has authority, influence, or primary association over a particular domain, aspect, or sphere of existence.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 10:45 p.m.