Triple
T14062084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Yuan |
E338370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol empire successor state |
C12380
|
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 empire successor state Context triple: [Great Yuan, instanceOf, Mongol empire successor state]
-
A.
Mongol successor state
chosen
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
-
B.
Byzantine successor state
A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
-
C.
post-imperial successor state
A post-imperial successor state is a political entity that emerges from the territorial, administrative, or institutional remnants of a dissolved empire, inheriting and adapting its structures, borders, and legacies.
-
D.
successor state of the Ming dynasty
The successor state of the Ming dynasty refers to any polity that claimed political, cultural, or dynastic continuity with the Ming after its fall in 1644, such as the Southern Ming regimes or later entities invoking Ming legitimacy.
-
E.
successor state of the Western Roman Empire
A successor state of the Western Roman Empire is a political entity that emerged in its former territories, inheriting and adapting Roman institutions, culture, and legal traditions while developing its own distinct identity.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.