Triple
T25096575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermogenianus |
E628604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial 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 official Context triple: [Hermogenianus, instanceOf, imperial official]
-
A.
imperial governor
An imperial governor is a high-ranking official appointed by a central empire to administer, oversee, and enforce its authority, laws, and policies within a specific province or territory.
-
B.
imperial court office
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
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.
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.
-
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. 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:25 a.m.