Triple
T15181898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian satraps |
E362766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial officials |
C29818
|
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 officials Context triple: [Persian satraps, instanceOf, imperial officials]
-
A.
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.
-
B.
imperial governor
chosen
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.
-
C.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
D.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
-
E.
Ottoman provincial governors
Ottoman provincial governors were imperial officials appointed by the sultan to administer provinces, collect taxes, maintain order, and implement central policies while balancing local power structures within the Ottoman Empire.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:09 a.m.