Triple
T32787217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland East Cushitic |
E838530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Afroasiatic languages |
C60021
|
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: subgroup of Afroasiatic languages Context triple: [Highland East Cushitic, instanceOf, subgroup of Afroasiatic languages]
-
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.
subgroup of Niger–Congo languages
A subgroup of Niger–Congo languages is a set of closely related languages within the Niger–Congo family that share a common ancestral origin and distinctive structural and lexical features.
-
C.
Afroasiatic language variety
An Afroasiatic language variety is a specific form or dialect of a language belonging to the Afroasiatic family, characterized by shared structural features and historical origins across regions of North Africa, the Horn of Africa, and parts of the Middle East.
-
D.
Aslian language subgroup
The Aslian language subgroup comprises a cluster of closely related Austroasiatic languages spoken primarily by indigenous Orang Asli communities in Peninsular Malaysia and southern Thailand.
-
E.
Cushitic language subgroup
chosen
A Cushitic language subgroup is a branch within the Cushitic family of Afroasiatic languages, comprising closely related languages that share common historical origins and structural features.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.