Triple
T5882060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishar Tatar |
E130771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Tatar language |
C19072
|
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: variety of the Tatar language Context triple: [Mishar Tatar, instanceOf, variety of the Tatar language]
-
A.
variety of Tajik language
A variety of Tajik language is a regional or social form of Tajik distinguished by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other forms of Tajik.
-
B.
variety of Belarusian language
A variety of the Belarusian language is a regionally or socially distinct form of Belarusian characterized by specific phonological, lexical, and grammatical features within the broader Belarusian linguistic system.
-
C.
variety of Turkish
A variety of Turkish is a distinct form or dialect of the Turkish language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
D.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
E.
variety of the Albanian language
A variety of the Albanian language is a distinct, systematically patterned form of Albanian—such as a dialect, sociolect, or regional speech form—characterized by unique phonological, lexical, and grammatical features within the broader Albanian linguistic continuum.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:57 p.m.