Triple
T34220162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuzhener dialect |
E877901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Hill Mari |
C59082
|
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 Hill Mari Context triple: [Kuzhener dialect, instanceOf, regional variety of Hill Mari]
-
A.
Hill Mari language
chosen
Hill Mari language is a Uralic language spoken primarily in the hilly regions of the Mari El Republic in Russia, characterized by its distinct phonology and grammar compared to Meadow Mari.
-
B.
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.
-
C.
regional variety of Mam
A regional variety of Mam is a distinct dialect or form of the Mam language spoken in a specific geographic area, characterized by unique phonological, lexical, and grammatical features.
-
D.
Mari language variety
A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-speaking community.
-
E.
Rarámuri language variety
A Rarámuri language variety is a specific regional or social form of the Rarámuri (Tarahumara) language, distinguished by its unique phonological, lexical, and grammatical features within the broader Rarámuri linguistic continuum.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.