Triple
T24583603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Momo languages |
E608319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bantoid languages subgroup |
C20849
|
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: Bantoid languages subgroup Context triple: [Momo languages, instanceOf, Bantoid languages subgroup]
-
A.
Bantoid languages
chosen
Bantoid languages are a branch of the Benue–Congo family within the Niger–Congo language phylum, comprising Bantu and closely related non-Bantu languages spoken primarily in Central and West Africa.
-
B.
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.
-
C.
Penutian languages subgroup
The Penutian languages subgroup is a proposed family of Native American languages, primarily spoken in western North America, that are hypothesized to share a common ancestral origin based on structural and lexical similarities.
-
D.
subfamily of Tupian languages
A subfamily of Tupian languages is a smaller, genetically related group of languages within the larger Tupian family that share a more recent common ancestor and distinctive linguistic features.
-
E.
Southwestern Tai languages subgroup
The Southwestern Tai languages subgroup comprises a branch of the Tai language family spoken primarily in mainland Southeast Asia, including Thai, Lao, and related regional languages that share common historical and linguistic 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.