Triple
T28324250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Former Yan |
E717363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Xianbei-led regime |
C53890
|
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: Xianbei-led regime Context triple: [Former Yan, instanceOf, Xianbei-led regime]
-
A.
Jurchen-led state
A Jurchen-led state is a political entity in which the Jurchen people hold primary ruling authority, shaping its governance, military organization, and cultural policies.
-
B.
nomadic empire
A nomadic empire is a large, often militaristic polity built and ruled by mobile pastoral or steppe peoples who control vast territories and diverse sedentary populations without fully settling them.
-
C.
Southern Dynasties dynasty
The Southern Dynasties dynasty refers collectively to the succession of four Chinese dynasties—Liu Song, Southern Qi, Liang, and Chen—that ruled southern China between 420 and 589 CE during a period of political division and cultural flourishing.
-
D.
Oghuz Turkic polity
An Oghuz Turkic polity is a socio-political entity formed by Oghuz Turkic groups, typically characterized by tribal confederation structures, nomadic or semi-nomadic lifeways, and rule by military-elite lineages asserting authority over diverse subject populations.
-
E.
Mongol imperial dynasty branch
A Mongol imperial dynasty branch is a distinct ruling line or subdivision of the broader Mongol imperial family that governed a specific territory or khanate while sharing common ancestry and political heritage with the main Mongol Empire.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:26 a.m.