Triple
T2997928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göklen dialect |
E81115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Turkmen language |
C3816
|
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 Turkmen language Context triple: [Göklen dialect, instanceOf, variety of Turkmen language]
-
A.
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.
-
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.
Turkic language
A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
-
D.
Oghuz language
chosen
The Oghuz language is a member of the Oghuz branch of the Turkic language family, historically spoken by the Oghuz Turks and forming the basis of several modern languages such as Turkish, Azerbaijani, and Turkmen.
-
E.
Nuristani language
A Nuristani language is any member of a small group of Indo-Iranian languages spoken primarily in the remote Nuristan region of eastern Afghanistan and adjacent areas of Pakistan.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:59 p.m.