Triple
T25238329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauravi dialect |
E632397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional dialect of Hindi-Urdu |
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: regional dialect of Hindi-Urdu Context triple: [Kauravi dialect, instanceOf, regional dialect of Hindi-Urdu]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:07 p.m.