Triple
T5240661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayı tribe |
E118331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Oghuz Turkic tribe |
C16972
|
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: Oghuz Turkic tribe Context triple: [Kayı tribe, instanceOf, Oghuz Turkic tribe]
-
A.
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.
-
B.
Turco-Mongol
Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
-
C.
Mongolic people
Mongolic people are an ethno-linguistic group originating from the Mongolian Plateau, historically associated with nomadic pastoralism and the Mongol Empire, and today encompassing various Mongol-speaking populations across Mongolia, China, Russia, and neighboring regions.
-
D.
Sarmatian people
The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
-
E.
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.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:49 p.m.