Triple
T15777951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah Mir dynasty |
E382536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sultanate of Kashmir |
C7900
|
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: Sultanate of Kashmir Context triple: [Shah Mir dynasty, instanceOf, Sultanate of Kashmir]
-
A.
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.
-
B.
Sultanate
chosen
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.
-
C.
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.
-
D.
Fulani Islamic state
A Fulani Islamic state is a political entity historically or conceptually governed by Fulani elites under Islamic law, combining Fulani cultural leadership with the religious, legal, and administrative frameworks of Islam.
-
E.
Bugis principality
A Bugis principality is a traditional political entity or small sovereign state historically governed by Bugis rulers in South Sulawesi, Indonesia, characterized by its own leadership, territory, and customary laws.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.