Triple
T28036574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horqin Mongols |
E708424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol subgroup |
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 subgroup Context triple: [Horqin Mongols, instanceOf, Mongol subgroup]
-
A.
Aimaq subgroup
Aimaq subgroup refers to a distinct tribal or regional division within the Aimaq people of Afghanistan and neighboring areas, characterized by shared lineage, dialect, and cultural practices.
-
B.
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.
-
C.
Gond subgroup
A Gond subgroup is a distinct clan or community division within the larger Gond ethnic group, characterized by shared ancestry, cultural practices, and social organization.
-
D.
Subanen subgroup
A Subanen subgroup is a distinct local or kin-based community within the broader Subanen ethnolinguistic group of the southern Philippines, characterized by shared dialectal, cultural, and territorial identities.
-
E.
Saxon subgroup
A Saxon subgroup is a subgroup of a group that satisfies specific structural or algebraic conditions related to the behavior of its elements under conjugation and interaction with other subgroups, often studied in the context of finite group theory.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:21 p.m.