Triple
T32623120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassa language |
E833983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kru language |
C8292
|
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: Kru language Context triple: [Bassa language, instanceOf, Kru language]
-
A.
Katuic language
A Katuic language is a member of a subgroup of the Austroasiatic language family spoken primarily by Katuic ethnic groups in Laos, Vietnam, and neighboring regions, characterized by complex phonologies and rich systems of verbal morphology.
-
B.
Korandje language
The Korandje language is a highly endangered Northern Songhay language spoken by a small community in the oasis town of Tabelbala in southwestern Algeria, notable for its extensive contact-induced influences from Berber and Arabic.
-
C.
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.
-
D.
Kwa language
chosen
Kwa language is a proposed branch of the Niger-Congo language family spoken primarily in southeastern Côte d’Ivoire, Ghana, Togo, and Benin, characterized by tonal systems and isolating to mildly agglutinative morphology.
-
E.
Grassfields language
A Grassfields language is a member of a subgroup of Southern Bantoid languages spoken primarily in the Grassfields region of western Cameroon, characterized by complex noun class systems and tonal distinctions.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.