Triple
T37048120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Gur |
E916974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Gur languages |
C62744
|
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 Gur languages Context triple: [Northern Gur, instanceOf, subgroup of Gur languages]
-
A.
Gur language subgroup
chosen
The Gur language subgroup is a branch of the Niger-Congo language family comprising numerous related languages spoken primarily in Burkina Faso, northern Ghana, Togo, Benin, and neighboring regions of West Africa.
-
B.
Palaungic language subgroup
The Palaungic language subgroup is a branch of the Austroasiatic language family comprising several closely related languages spoken primarily by Palaung and related ethnic groups in Myanmar, China, Laos, and neighboring regions.
-
C.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
D.
Guang language subgroup
The Guang language subgroup is a branch of the Niger-Congo language family comprising closely related languages spoken primarily in Ghana and parts of neighboring West African countries.
-
E.
Tibeto-Burman languages subgroup
The Tibeto-Burman languages subgroup is a major branch of the Sino-Tibetan language family comprising hundreds of related languages spoken primarily in the Himalayas, Southeast Asia, and parts of East Asia.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.