Triple
T37348476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Damara-Nama |
E927247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Khoisan language variety |
C30070
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Khoisan language variety Context triple: [Damara-Nama, instanceOf, Khoisan language variety]
-
A.
Central Khoisan language
chosen
A Central Khoisan language is a member of the Khoisan language family spoken primarily in central southern Africa, characterized by extensive use of click consonants and complex phonological systems.
-
B.
Makhuwa language variety
A Makhuwa language variety is a specific regional or social form of the Makhuwa Bantu language, distinguished by its own phonological, lexical, or grammatical features within the broader Makhuwa linguistic continuum.
-
C.
Tswa–Ronga language variety
A Tswa–Ronga language variety is a specific regional or social form of the Tswa–Ronga language cluster, characterized by distinct phonological, lexical, and grammatical features shared by its speakers.
-
D.
Noongar language variety
A Noongar language variety is a specific regional or dialectal form of the Noongar Aboriginal language spoken in southwestern Western Australia, characterized by distinct phonological, lexical, and grammatical features within the broader Noongar language continuum.
-
E.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
- F. None of above.
Provenance (1 batch)
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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.