Triple
T31737572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Song |
E810045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Han dynasty official |
C59136
|
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: Eastern Han dynasty official Context triple: [Cao Song, instanceOf, Eastern Han dynasty official]
-
A.
Tang dynasty official
A Tang dynasty official is a government administrator or bureaucrat serving the Tang Empire, typically selected through the imperial examination system to manage civil, military, and fiscal affairs.
-
B.
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.
-
C.
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.
-
D.
Eastern Wu politician
An Eastern Wu politician is a government official or statesman who served in the bureaucracy or court of the Eastern Wu state during China’s Three Kingdoms period, influencing its domestic policies, administration, and diplomatic or military decisions.
-
E.
Western Han noble
A Western Han noble is a high-ranking aristocrat in the Western Han Dynasty who holds hereditary titles, land, and political influence within the imperial hierarchy.
- F. None of above. chosen
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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:23 p.m.