Triple
T27696622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Jun |
E698312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Han dynasty general |
C40471
|
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: Han dynasty general Context triple: [Zhu Jun, instanceOf, Han dynasty general]
-
A.
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.
-
B.
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.
-
C.
Eastern Wu general
An Eastern Wu general is a high-ranking military commander serving the state of Eastern Wu during China’s Three Kingdoms period, responsible for leading armies, defending territories, and executing strategic campaigns.
-
D.
Ming dynasty general
A Ming dynasty general is a high-ranking military commander serving the Ming imperial court, responsible for leading armies, defending borders, and enforcing the emperor’s authority across the empire.
-
E.
Chinese military figure
chosen
A Chinese military figure is an individual from any period of Chinese history who holds or has held a position of command, leadership, or strategic influence within China’s armed forces or military institutions.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:54 p.m.