Triple
T14554738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Jin |
E341508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Manchu-led state |
C14309
|
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: Manchu-led state Context triple: [Later Jin, instanceOf, Manchu-led state]
-
A.
Jurchen-led state
chosen
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.
institution of the Qing dynasty
An institution of the Qing dynasty is a formal political, administrative, military, social, or cultural organization or system established or sanctioned by the Qing imperial government to govern, regulate, and structure life within the empire.
-
C.
Mongol successor state
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.
-
D.
Chinese political dynasty
A Chinese political dynasty is a historically distinct period of rule in China characterized by a hereditary ruling family that maintains centralized authority, legitimized by cultural, ideological, and bureaucratic institutions, until replaced by another ruling house.
-
E.
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.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.