Triple
T6922323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadaksahak language |
E160217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Afroasiatic-influenced language |
C21347
|
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: Afroasiatic-influenced language Context triple: [Tadaksahak language, instanceOf, Afroasiatic-influenced language]
-
A.
Afroasiatic language branch
The Afroasiatic language branch is a major language family originating in the Middle East and North Africa, encompassing diverse languages such as Arabic, Hebrew, Amharic, and Hausa that share common historical and structural features.
-
B.
Semitic language
A Semitic language is a member of a family of related languages originating in the Middle East and North Africa, characterized by root-based morphology and including languages such as Arabic, Hebrew, and Amharic.
-
C.
Nilo-Saharan language
A Nilo-Saharan language is a member of a proposed but controversial language family spoken primarily along the Nile and across parts of central and eastern Africa, characterized by significant internal diversity and debated genetic relationships.
-
D.
Cushitic language
A Cushitic language is a member of a branch of the Afroasiatic language family spoken primarily in the Horn of Africa and parts of East Africa, characterized by shared grammatical and phonological features distinct from other Afroasiatic branches.
-
E.
Atlantic-Congo language
An Atlantic-Congo language is a member of a major branch of the Niger-Congo language family, encompassing a vast and diverse group of languages spoken primarily in sub-Saharan Africa.
- F. None of above. chosen
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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:26 p.m.