Triple
T36045860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thakri language |
E1042668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Indo-Aryan language |
C6327
|
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: Southern Indo-Aryan language Context triple: [Thakri language, instanceOf, Southern Indo-Aryan 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.
Indo-Aryan language variety
chosen
An Indo-Aryan language variety is a specific form or dialect of a language within the Indo-Aryan branch of the Indo-European family, characterized by shared historical origins and linguistic features such as phonology, grammar, and vocabulary.
-
C.
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.
-
D.
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.
-
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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.