Triple
T35603501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barmer Marwari |
E1028818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Marwari |
C11601
|
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 Marwari Context triple: [Barmer Marwari, instanceOf, regional variety of Marwari]
-
A.
Rajasthani dialect
chosen
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.
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.
-
C.
regional variety of Garhwali
A regional variety of Garhwali is a localized form of the Garhwali language distinguished by its unique phonological, lexical, and syntactic features specific to a particular area within the Garhwal region.
-
D.
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.
-
E.
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.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.