Triple
T24143159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merkit tribe |
E598299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongolic tribe |
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: Mongolic tribe Context triple: [Merkit tribe, instanceOf, Mongolic tribe]
-
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.
Aimaq tribe
The Aimaq tribe is a collection of semi-nomadic Persian-speaking tribal groups primarily inhabiting western and central Afghanistan, known for their distinct cultural traditions and pastoral lifestyle.
-
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.
Naga tribe
A Naga tribe is an indigenous ethnic community from the northeastern region of India and northwestern Myanmar, characterized by distinct languages, rich oral traditions, and unique cultural practices including elaborate festivals and traditional attire.
-
E.
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.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:29 p.m.