Triple
T28876606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanoli Hindko |
E732286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Hindko |
C5291
|
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 Hindko Context triple: [Tanoli Hindko, instanceOf, regional variety of Hindko]
-
A.
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.
-
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.
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.
-
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.
variety of Punjabi language
chosen
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.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:38 a.m.