Triple
T34613824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeng Guofan |
E888808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty statesman |
C31546
|
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: Qing dynasty statesman Context triple: [Zeng Guofan, instanceOf, Qing dynasty statesman]
-
A.
Qing dynasty viceroy
A Qing dynasty viceroy was a high-ranking imperial official who governed one or more provinces, overseeing civil administration, military affairs, and tax collection on behalf of the emperor.
-
B.
Qing dynasty general
chosen
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.
ancient Chinese statesman
An ancient Chinese statesman is a high-ranking political figure who advised rulers, administered government affairs, and shaped state policies within the historical dynasties of China.
-
D.
Qin dynasty politician
A Qin dynasty politician was an official or statesman who served in the central or regional administration of the Qin state or empire (221–206 BCE), helping implement its legalist policies, bureaucratic reforms, and imperial governance.
-
E.
Yuan dynasty official
A Yuan dynasty official was an appointed administrator or bureaucrat serving under the Mongol-led Yuan Empire (1271–1368), responsible for implementing imperial policies, managing local governance, and overseeing taxation and legal affairs within a hierarchical, often ethnically stratified, governmental system.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.