Triple
T8379749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dabir-ul-Mulk |
E197658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal administrative title |
C13577
|
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 title Context triple: [Dabir-ul-Mulk, instanceOf, Mughal administrative title]
-
A.
Ottoman court title
An Ottoman court title is an official designation granted within the Ottoman imperial hierarchy that denotes a person's rank, role, and privileges in the administration, judiciary, or royal household.
-
B.
Mughal official
chosen
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.
-
C.
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.
-
D.
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.
-
E.
colonial-style administrative position
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:02 p.m.