Triple
T30496652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedareb |
E776024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cushitic-speaking people |
C8777
|
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: Cushitic-speaking people Context triple: [Hedareb, instanceOf, Cushitic-speaking people]
-
A.
Cushitic people
chosen
Cushitic people are a diverse group of ethnolinguistic communities in the Horn of Africa and surrounding regions who speak Cushitic languages, a branch of the Afroasiatic language family, and share related cultural and historical traditions.
-
B.
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.
-
C.
Semitic-speaking people
Semitic-speaking people are groups whose native languages belong to the Semitic branch of the Afroasiatic language family, historically including communities such as Arabs, Jews, Assyrians, and others across the Middle East and surrounding regions.
-
D.
Gbe-speaking people
Gbe-speaking people are a culturally related group of West African ethnic communities, primarily in present-day Ghana, Togo, Benin, and Nigeria, who share closely related Gbe languages and intertwined historical, religious, and social traditions.
-
E.
Luri-speaking people
Luri-speaking people are an Iranian ethnic group primarily inhabiting western and southwestern Iran, characterized by their use of the Luri language and distinct cultural traditions.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:14 p.m.