Triple
T16026065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qipchaq Uzbek |
E388720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Uzbek language |
C36857
|
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 Uzbek language Context triple: [Qipchaq Uzbek, instanceOf, variety of the Uzbek 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 the Tatar language
A variety of the Tatar language is a regionally or socially distinct form of Tatar characterized by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other Tatar forms.
-
C.
variety of Urdu
A variety of Urdu is a distinct form of the Urdu language characterized by unique phonological, lexical, syntactic, and sociolinguistic features associated with a particular region, community, or context.
-
D.
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.
-
E.
variety of Ossetian language
A variety of Ossetian language is a distinct regional or social form of Ossetian characterized by specific phonological, lexical, and grammatical features within the broader Ossetian 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.