Triple
T11024379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-North Dravidian |
E260577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Dravidian language |
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: North Dravidian language Context triple: [Proto-North Dravidian, instanceOf, North Dravidian language]
-
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.
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.
-
C.
Dravidian people
Dravidian people are a diverse group of ethnolinguistic communities in South Asia, primarily in southern India and parts of Sri Lanka, who speak Dravidian languages and share related cultural and historical traditions.
-
D.
Tai-Kadai language
A Tai-Kadai language is a member of a family of tonal languages spoken primarily in Southeast Asia and southern China, characterized by similar phonological, lexical, and grammatical features that suggest a common historical origin.
-
E.
regional language of India
A regional language of India is a native tongue predominantly spoken within a specific geographic area of the country, reflecting its unique cultural, historical, and social identity.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.