Triple
T28239263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghiyasuddin Mahmud Shah |
E711974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Last sultan of the Bengal Sultanate |
C54576
|
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: Last sultan of the Bengal Sultanate Context triple: [Ghiyasuddin Mahmud Shah, instanceOf, Last sultan of the Bengal Sultanate]
-
A.
last sultan of the Great Seljuk Empire
The last sultan of the Great Seljuk Empire is the final reigning monarch who held supreme political and military authority over the Seljuk domains before the empire’s ultimate fragmentation and decline.
-
B.
Sultan of Gujarat
The Sultan of Gujarat was the sovereign ruler of the Gujarat Sultanate, a medieval Islamic kingdom in western India known for its maritime trade, cultural patronage, and strategic political influence from the 15th to 16th centuries.
-
C.
last ruler of a princely state
The last ruler of a princely state is the final sovereign or monarch who held authority over a semi-autonomous regional kingdom or territory before its dissolution, annexation, or integration into a larger political entity.
-
D.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
-
E.
Sultan of Ahmadnagar
The Sultan of Ahmadnagar was the sovereign ruler of the Ahmadnagar Sultanate in the Deccan region of India, holding political, military, and administrative authority over the state and its territories.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:57 p.m.