Triple
T19975682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundelkhandi Hindi |
E493684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Hindi dialect |
C7534
|
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: Western Hindi dialect Context triple: [Bundelkhandi Hindi, instanceOf, Western Hindi dialect]
-
A.
Rajasthani dialect
Rajasthani dialect is a regional linguistic variety spoken in the Indian state of Rajasthan, characterized by its distinct phonetics, vocabulary, and grammar that differentiate it from standard Hindi and other neighboring languages.
-
B.
Gujarati dialect
A Gujarati dialect is a regional or social variety of the Gujarati language characterized by distinct phonological, lexical, and grammatical features used by specific communities within Gujarati-speaking regions.
-
C.
Hindi-Urdu dialect
chosen
A Hindi-Urdu dialect is a regional or social variety of the Hindustani language continuum, characterized by distinct phonological, lexical, and sometimes script-based features shaped by local culture and history.
-
D.
Punjabi dialect
A Punjabi dialect is a regional or social variety of the Punjabi language characterized by distinct pronunciation, vocabulary, and grammatical features used by specific communities within Punjabi-speaking areas.
-
E.
Chhattisgarhi dialect
The Chhattisgarhi dialect is an Indo-Aryan language variety spoken primarily in the Indian state of Chhattisgarh, characterized by its distinct phonology, vocabulary, and grammatical features that differentiate it from Standard Hindi.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:25 p.m.