Triple
T20104868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal Subah of Orissa |
E490141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | province of the Mughal Empire |
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: province of the Mughal Empire Context triple: [Mughal Subah of Orissa, instanceOf, province of the Mughal Empire]
-
A.
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.
-
B.
district of British India
A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
-
C.
province of the Abbasid Caliphate
A province of the Abbasid Caliphate is an administrative territorial unit governed by a caliphal-appointed official responsible for local governance, tax collection, security, and implementation of central policies within the empire.
-
D.
ruling dynasty of North India
A ruling dynasty of North India is a hereditary line of monarchs or sovereign families that exercised political authority, controlled territory, and shaped the region’s cultural, social, and economic life over successive generations.
-
E.
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.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:28 p.m.