Triple
T22325304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xu Shuzheng |
E551886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Beiyang clique general |
C25358
|
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: Beiyang clique general Context triple: [Xu Shuzheng, instanceOf, Beiyang clique general]
-
A.
Beiyang clique warlord
chosen
A Beiyang clique warlord is a military strongman from the early Republic of China who, emerging from Yuan Shikai’s Beiyang Army, controlled territory and political power through armed force and factional alliances during the Warlord Era.
-
B.
Beiyang clique leader
A Beiyang clique leader was a powerful Chinese military and political figure from the early Republican era who commanded factions of the Beiyang Army to control territories, influence national politics, and compete with rival warlords.
-
C.
Zhili clique leader
A Zhili clique leader is a high-ranking military or political figure who commands and directs the factional interests, strategies, and operations of the Zhili clique within the broader context of early 20th-century Chinese warlord politics.
-
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.
Beiyang clique member
A Beiyang clique member is an individual affiliated with the powerful military-political faction that emerged from Yuan Shikai’s Beiyang Army and dominated Chinese warlord politics in the early Republic of China.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.