Triple
T28187442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Councillors |
E716216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial Chinese official |
C49436
|
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: imperial Chinese official Context triple: [Grand Councillors, instanceOf, imperial Chinese official]
-
A.
imperial official
chosen
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.
-
B.
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.
-
C.
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.
-
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.
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.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:23 p.m.