Triple
T8802387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil–Kurumba subgroup |
E209442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Southern Dravidian languages |
C1109
|
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 Southern Dravidian languages Context triple: [Tamil–Kurumba subgroup, instanceOf, branch of Southern Dravidian languages]
-
A.
Dravidian language
chosen
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
branch of Khoe–Kwadi
A branch of Khoe–Kwadi is a subgroup within the Khoe–Kwadi language family that comprises closely related languages or dialects sharing common historical and structural 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:44 p.m.