Triple
T6108431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borjigin |
E136172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol clan |
C13412
|
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: Mongol clan Context triple: [Borjigin, instanceOf, Mongol clan]
-
A.
Mongolic people
chosen
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.
-
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.
Oghuz Turkic tribe
An Oghuz Turkic tribe is a socio-political and kinship-based group descended from the historical Oghuz Turks, sharing common lineage, language, and cultural traditions within the broader Oghuz Turkic world.
-
D.
Oghuz Turk
An Oghuz Turk is a member of a historical western Turkic tribal confederation whose descendants include many modern Turkic peoples such as Turks of Turkey, Azerbaijanis, and Turkmen.
-
E.
Mongolic language
A Mongolic language is any member of a family of closely related languages spoken primarily in Mongolia, northern China, and surrounding regions, characterized by agglutinative morphology and subject–object–verb word order.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:13 p.m.