Triple
T19233792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subahdar of Gujarat |
E480939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal provincial office |
C1201
|
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: Mughal provincial office Context triple: [Subahdar of Gujarat, instanceOf, Mughal provincial office]
-
A.
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.
-
B.
Mughal court institution
A Mughal court institution is a formal administrative, ceremonial, or advisory body within the Mughal imperial court that structured governance, hierarchy, and cultural life of the empire.
-
C.
Mughal official
A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
-
D.
subah of the Mughal Empire
chosen
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
-
E.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:26 p.m.