Triple
T2998755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andaman Hindi |
E81134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Hindi |
C6327
|
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 Context triple: [Andaman Hindi, instanceOf, regional variety of Hindi]
-
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.
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.
-
C.
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.
-
D.
Hindi-Urdu dialect
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.
-
E.
Indo-Aryan language variety
chosen
An Indo-Aryan language variety is a specific form or dialect of a language within the Indo-Aryan branch of the Indo-European family, characterized by shared historical origins and linguistic features such as phonology, grammar, and vocabulary.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:59 p.m.