Triple
T7660909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gondi–Kui subgroup |
E173502
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of 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 Dravidian languages Context triple: [Gondi–Kui subgroup, instanceOf, branch of 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.
branch of Iranian languages
A branch of Iranian languages is a subgroup within the Iranian language family comprising closely related languages that share a common historical origin, structural features, and geographic distribution.
-
E.
branch of Semitic languages
A branch of Semitic languages is a subgroup within the Semitic language family comprising closely related languages that share common historical origins, structural features, and vocabulary.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.