Triple
T8809258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabiye |
E209614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gur language |
C25098
|
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: Gur language Context triple: [Kabiye, instanceOf, Gur language]
-
A.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
-
B.
Ubangian language
A Ubangian language is a member of a proposed group of Central African languages, primarily spoken in the Central African Republic and neighboring countries, that share common phonological and grammatical features and are often considered a branch of the Niger-Congo family.
-
C.
Hurro-Urartian language
A Hurro-Urartian language is a member of an extinct family of ancient Near Eastern languages, primarily known from cuneiform inscriptions of the Hurrians and Urartians in the second and first millennia BCE.
-
D.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
-
E.
Zenati language
The Zenati language is a conceptual class representing a branch of Berber languages characterized by shared phonological, morphological, and lexical features that distinguish it from other Afroasiatic language groups.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.