Triple
T3655174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu’l-Fazl ibn Mubarak |
E77511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal official |
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 official Context triple: [Abu’l-Fazl ibn Mubarak, instanceOf, Mughal official]
-
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.
Nawab
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
-
C.
Governor-General of Bengal
The Governor-General of Bengal was the chief British official in colonial Bengal, later evolving into the de facto head of British administration in India, responsible for overseeing governance, revenue, and foreign affairs in the region.
-
D.
Hindu ruler
A Hindu ruler is a sovereign or monarch who governs a territory while adhering to, promoting, or being culturally shaped by Hindu religious, social, and philosophical traditions.
-
E.
Abbasid official
An Abbasid official was a bureaucrat or administrator serving the Abbasid Caliphate, responsible for managing state affairs such as taxation, justice, military logistics, and provincial governance within the empire’s centralized administrative system.
- F. None of above. chosen
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.