Triple
T636455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balkan Turkish |
E16632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Turkish |
C3815
|
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 Turkish Context triple: [Balkan Turkish, instanceOf, regional variety of Turkish]
-
A.
colloquial Arabic variety
A colloquial Arabic variety is a regionally or socially specific, primarily spoken form of Arabic that differs from Modern Standard Arabic in pronunciation, vocabulary, and grammar.
-
B.
Greek language variety
A Greek language variety is a distinct form of the Greek language, characterized by specific phonological, grammatical, lexical, and pragmatic features associated with particular regions, communities, or social groups.
-
C.
variety of the Greek language
A variety of the Greek language is a distinct form or dialect of Greek, characterized by specific phonological, grammatical, lexical, and pragmatic features used by a particular community or in a particular context.
-
D.
Oghuz language
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.
Turkic language
chosen
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.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.