Triple
T3042446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyr dialect |
E83161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of language |
C3176
|
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 language Context triple: [Salyr dialect, instanceOf, regional variety of language]
-
A.
spoken language variety
chosen
A spoken language variety is a distinct form of a language as it is actually spoken by a particular group of people, characterized by specific phonological, lexical, and grammatical features.
-
B.
macrolanguage variety
A macrolanguage variety is a specific linguistic form or set of forms that functions as one distinguishable member within a broader macrolanguage encompassing multiple closely related or mutually recognized language varieties.
-
C.
group of language varieties
A group of language varieties is a conceptual class encompassing related dialects, sociolects, or registers that share a common linguistic base but differ in systematic ways across regions, communities, or contexts.
-
D.
standardized language variety
A standardized language variety is a codified form of a language that has been deliberately regulated and accepted as the norm for public, official, and educational use within a speech community.
-
E.
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.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:01 p.m.