Triple
T15703753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain-i Akbari |
E380656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal administrative manual |
C35216
|
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 administrative manual Context triple: [Ain-i Akbari, instanceOf, Mughal administrative manual]
-
A.
Mughal court chronicle
A Mughal court chronicle is an official historical narrative, often commissioned by the emperor, that records the political events, administrative affairs, cultural life, and imperial ideology of the Mughal court.
-
B.
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.
-
C.
Mughal-era legal code
A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
-
D.
Mughal court institution
chosen
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.
-
E.
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.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.