Triple
T37855330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habsburg administration in Italy |
E944174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | system of imperial governance |
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: system of imperial governance Context triple: [Habsburg administration in Italy, instanceOf, system of imperial governance]
-
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.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
-
C.
instrument of colonial administration
An instrument of colonial administration is any institutional mechanism, policy, or practice deliberately used by a colonial power to govern, control, and extract resources from colonized populations and territories.
-
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.
royal administration apparatus
The royal administration apparatus is the organized system of offices, officials, and procedures through which a monarchy governs, manages resources, and enforces its authority over a realm.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.