Triple
T28129351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanyan Zonghan |
E711018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jurchen general |
C29687
|
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: Jurchen general Context triple: [Wanyan Zonghan, instanceOf, Jurchen general]
-
A.
Jurchen chieftain
chosen
A Jurchen chieftain is a hereditary or militarily ascendant leader of a Jurchen tribal group who exercises political, military, and economic authority within the broader context of Northeast Asian steppe-forest societies.
-
B.
Chu general
A Chu general is a high-ranking military commander from the ancient Chinese state of Chu, responsible for leading armies, planning campaigns, and defending or expanding the state's territories.
-
C.
Genghis Khan general
A Genghis Khan general is a high-ranking military commander serving under Genghis Khan, responsible for leading Mongol armies, executing strategic campaigns, and enforcing the Khan’s authority across conquered territories.
-
D.
Qing dynasty general
A Qing dynasty general is a high-ranking military commander serving the Qing imperial government, responsible for leading troops, enforcing imperial authority, and managing regional defense and campaigns across the empire.
-
E.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:22 p.m.