Triple
T3655125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulh-i Kul |
E77510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal policy |
C1200
|
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 policy Context triple: [Sulh-i Kul, instanceOf, Mughal policy]
-
A.
subah of the Mughal Empire
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.
-
B.
colonial policy
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
-
C.
Maratha fiscal levy
A Maratha fiscal levy is a tax or tribute imposed by the Maratha state on agrarian produce, trade, or territories under its influence, serving as a key instrument of revenue extraction and political control.
-
D.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
E.
early modern Indian polity
chosen
Early modern Indian polity refers to the complex, regionally diverse systems of governance, authority, and political negotiation that emerged in the Indian subcontinent roughly between the 16th and 18th centuries, encompassing empires, kingdoms, and local powers interacting through warfare, diplomacy, and administration.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:24 p.m.