Triple
T7650404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeseri (Dweep Bhasha) |
E173235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Aryan–influenced Dravidian lect |
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: Indo-Aryan–influenced Dravidian lect Context triple: [Jeseri (Dweep Bhasha), instanceOf, Indo-Aryan–influenced Dravidian lect]
-
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.
Hindustani lect
A Hindustani lect is a particular regional or social variety within the Hindustani language continuum, encompassing specific patterns of pronunciation, vocabulary, and grammar used by a distinct speech community.
-
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.
classical language of India
A classical language of India is an ancient, historically significant Indian language with a rich literary tradition and documented history over a long period, recognized for its cultural and scholarly importance.
-
E.
Indo-Aryan people
Indo-Aryan people are a diverse group of ethnolinguistic communities in South Asia who speak Indo-Aryan languages, a major branch of the Indo-European language family, and share related historical and cultural roots.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:58 p.m.