Triple
T7344490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garhwali |
E169341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional language of India |
C22033
|
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 language of India Context triple: [Garhwali, instanceOf, regional language of India]
-
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.
classical language of India
A classical language of India is an ancient, historically significant Indian language with a rich literary tradition and documented history over a long period, recognized for its cultural and scholarly importance.
-
E.
regional language of Indonesia
A regional language of Indonesia is a native language spoken by a specific ethnic group or community within the Indonesian archipelago, distinct from the national language Bahasa Indonesia and used in local daily communication, culture, and traditions.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:05 p.m.