Triple
T32672009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota–Toda |
E835321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dravidian language subgroup |
C24648
|
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: Dravidian language subgroup Context triple: [Kota–Toda, instanceOf, Dravidian language subgroup]
-
A.
Dravidian language
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.
Aslian language subgroup
The Aslian language subgroup comprises a cluster of closely related Austroasiatic languages spoken primarily by indigenous Orang Asli communities in Peninsular Malaysia and southern Thailand.
-
C.
branch of the Dravidian language family
chosen
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.
-
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.
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.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.