Triple
T19369769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Gondi |
E484500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Dravidian language |
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: Central Dravidian language Context triple: [Northern Gondi, instanceOf, Central Dravidian language]
-
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 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.
-
C.
Dardic language
A Dardic language is a member of a subgroup of the Indo-Aryan languages spoken primarily in the mountainous regions of northern Pakistan, northwestern India, and eastern Afghanistan, characterized by distinct phonological and lexical features.
-
D.
Bihari languages
Bihari languages are a group of closely related Indo-Aryan languages and dialects spoken primarily in the Indian state of Bihar and surrounding regions, including Bhojpuri, Maithili, and Magahi.
-
E.
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.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:35 p.m.