Triple
T1409454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamalpuri dialect |
E31771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety 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 variety of Bengali Context triple: [Jamalpuri dialect, instanceOf, regional variety of Bengali]
-
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.
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.
variety of Punjabi language
A variety of Punjabi language is a distinct regional or social form of Punjabi characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Punjabi forms.
-
D.
classical language variety
A classical language variety is a historically prestigious, standardized form of a language, typically preserved in literature and formal contexts, that differs from its modern spoken descendants.
-
E.
national variety of English
A national variety of English is a distinct form of the English language associated with a particular country, characterized by its own norms of pronunciation, vocabulary, grammar, and usage.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.