Triple
T30154805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Bing |
E766493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qin dynasty official |
C26606
|
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: Qin dynasty official Context triple: [Li Bing, instanceOf, Qin dynasty official]
-
A.
Qin dynasty politician
chosen
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.
-
B.
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.
-
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.
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.
-
E.
imperial official
An imperial official is a government functionary appointed by a sovereign empire to administer its laws, collect revenues, and enforce imperial authority within a designated jurisdiction.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:20 p.m.