Triple
T22672043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinajpuri dialect |
E560242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional dialect of Bengali |
C7535
|
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: regional dialect of Bengali Context triple: [Dinajpuri dialect, instanceOf, regional dialect of Bengali]
-
A.
regional variety of Bengali
chosen
A regional variety of Bengali is a localized form of the Bengali language characterized by distinct phonological, lexical, and sometimes grammatical features associated with a specific geographic area or speech community.
-
B.
regional variety of Odia
A regional variety of Odia is a geographically localized form of the Odia language characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
-
C.
Odia dialect
Odia dialect refers to any regional or social variety of the Odia language, characterized by distinct phonological, lexical, and syntactic features used by specific communities within Odisha and neighboring regions.
-
D.
regional variety of Indian English
A regional variety of Indian English is a localized form of English spoken in a specific part of India, shaped by the region’s native languages, cultural norms, and pronunciation patterns.
-
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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:10 p.m.