Triple
T7795669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karrani dynasty |
E180292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruling dynasty of Bengal Sultanate |
C12347
|
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: ruling dynasty of Bengal Sultanate Context triple: [Karrani dynasty, instanceOf, ruling dynasty of Bengal Sultanate]
-
A.
Bengal dynasty
chosen
The Bengal dynasty refers to the succession of ruling families and political powers that governed the Bengal region (in present-day Bangladesh and eastern India) across various historical periods, shaping its cultural, economic, and political development.
-
B.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
C.
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.
-
D.
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.
-
E.
Muslim dynasty
A Muslim dynasty is a ruling family or lineage that governs a territory or state over successive generations under Islamic political, cultural, and religious principles.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:31 p.m.