Triple
T33008395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rampuri dialect |
E844572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety 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 variety of Hindi-Urdu Context triple: [Rampuri dialect, instanceOf, regional variety of Hindi-Urdu]
-
A.
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.
-
B.
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.
-
C.
regional variety of Bengali
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.
-
D.
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.
-
E.
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.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.