Triple
T23758005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauryan mining administration |
E587172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial administrative system |
C6483
|
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 administrative system Context triple: [Mauryan mining administration, instanceOf, imperial administrative system]
-
A.
imperial institution
chosen
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
B.
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.
-
C.
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.
-
D.
Mughal administration
Mughal administration was a centralized imperial governance system in South Asia that combined Persian bureaucratic practices, a hierarchical mansabdari (rank) system, and regional autonomy to manage revenue, military, and justice across a diverse empire.
-
E.
imperial register
An imperial register is an official record-keeping system used by an empire to document subjects, territories, resources, decrees, and administrative actions for governance and control.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:14 p.m.