Triple
T23354771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Munda subgroup |
E593013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Munda languages |
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: branch of Munda languages Context triple: [South Munda subgroup, instanceOf, branch of Munda languages]
-
A.
branch of Austroasiatic languages
A branch of Austroasiatic languages is a subgroup within the Austroasiatic language family whose member languages share a common historical origin and distinctive linguistic features.
-
B.
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.
-
C.
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.
-
D.
branch of Bantu languages
A branch of Bantu languages is a subgroup within the Bantu language family whose member languages share a common historical origin and exhibit closely related grammatical, phonological, and lexical features.
-
E.
branch of the Dravidian language family
A branch of the Dravidian language family is a subgroup of related Dravidian languages that share a common historical origin, structural features, and linguistic innovations distinguishing them from other Dravidian subgroups.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:20 p.m.