Triple
T547289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi Sultanate |
E12760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Indian kingdom |
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: medieval Indian kingdom Context triple: [Delhi Sultanate, instanceOf, medieval Indian kingdom]
-
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.
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.
-
C.
presidency of British India
The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
-
D.
Islamic empire
An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
-
E.
Emperor of India
The "Emperor of India" was a sovereign title used by the British monarch from 1876 to 1948 to signify their supreme imperial authority over the territories of the Indian subcontinent under British rule.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.