Triple
T26351034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himba |
E662900
|
entity |
| Predicate | otjizeFunction |
P120653
|
FINISHED |
| Object | symbolic identity |
—
|
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: symbolic identity | Statement: [Himba, otjizeFunction, symbolic identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otjizeFunction Context triple: [Himba, otjizeFunction, symbolic identity]
-
A.
jawFunction
Indicates the functional role, movement, or mechanical action performed by a jaw in relation to other anatomical structures or processes.
-
B.
sestetFunction
Indicates the specific structural or thematic role that a sestet (a six-line poetic unit, often the final part of a sonnet) performs within a poem.
-
C.
functie
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
tribalFunction
chosen
Indicates a role, duty, or activity that a tribe or tribal group performs or is responsible for.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:45 p.m.