Triple
T28983779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kherwarian languages |
E734622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Munda language subgroup |
C24387
|
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: Munda language subgroup Context triple: [Kherwarian languages, instanceOf, Munda language subgroup]
-
A.
Munda languages subgroup
chosen
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.
-
B.
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.
-
C.
Grassfields language subgroup
The Grassfields language subgroup is a branch of the Southern Bantoid languages spoken primarily in the Grassfields region of western Cameroon, characterized by significant internal diversity and complex noun class systems.
-
D.
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.
-
E.
Yuman language subgroup
The Yuman language subgroup is a branch of the Yuman–Cochimí language family comprising closely related Indigenous languages spoken primarily along the lower Colorado River, in southwestern Arizona, southeastern California, and northern Baja California.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:13 a.m.