Triple
T6921746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalhora dynasty |
E160201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former ruling dynasty of Sindh |
C11026
|
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: former ruling dynasty of Sindh Context triple: [Kalhora dynasty, instanceOf, former ruling dynasty of Sindh]
-
A.
Bengal dynasty
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.
Persianate dynasty
A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
-
C.
Muslim dynasty
chosen
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.
-
D.
Nizam of Hyderabad
The Nizam of Hyderabad was the hereditary monarch and ruler of the princely state of Hyderabad in south-central India, known for immense wealth, semi-autonomous governance under British suzerainty, and a significant role in regional politics until the state's integration into the Indian Union in 1948.
-
E.
Sultanate
A Sultanate is a form of monarchy or state ruled by a sultan, typically characterized by Islamic governance traditions and varying degrees of centralized authority.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:26 p.m.