Triple
T3162534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nawab of the Carnatic |
E66133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subordinate ruler of the Mughal Empire |
C4231
|
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: subordinate ruler of the Mughal Empire Context triple: [Nawab of the Carnatic, instanceOf, subordinate ruler of the Mughal Empire]
-
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.
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.
-
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.
Nawab
chosen
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.
-
E.
office in the Maratha Empire
An office in the Maratha Empire was an administrative or military position within the Maratha governance structure, responsible for managing specific territorial, fiscal, or command duties under the authority of the Maratha rulers.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.