Triple
T8495810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vavuniya District (Tamil-speaking areas) |
E201095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tamil-speaking region |
C24529
|
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: Tamil-speaking region Context triple: [Vavuniya District (Tamil-speaking areas), instanceOf, Tamil-speaking region]
-
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.
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.
-
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.
South Indian kingdom
A South Indian kingdom is a historically or culturally defined political entity located in the southern part of the Indian subcontinent, characterized by distinct Dravidian languages, traditions, and regional governance.
-
E.
Telugu dialect
A Telugu dialect is a regional or social variety of the Telugu language characterized by distinct phonological, lexical, and syntactic features used by a specific speech community.
- F. None of above. chosen
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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:13 p.m.