Triple
T28634563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khitan people |
E724740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | para-Mongolic people |
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: para-Mongolic people Context triple: [Khitan people, instanceOf, para-Mongolic people]
-
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.
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.
-
C.
Karenic people
The Karenic people are an ethnolinguistic group indigenous to the border regions of Myanmar and Thailand, known for their diverse Karen languages, distinct cultural traditions, and varied religious practices.
-
D.
Samoyedic people
Samoyedic people are a group of indigenous peoples of northern Eurasia, primarily in northern Russia, who speak Samoyedic languages of the Uralic family and traditionally practice reindeer herding, fishing, and hunting in Arctic and subarctic environments.
-
E.
Nakh people
The Nakh people are a group of closely related Northeast Caucasian ethnic communities, primarily including the Chechens and Ingush, characterized by a shared Nakh language branch, highland cultural traditions, and historical presence in the North Caucasus region.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:39 a.m.