Triple
T27756995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saifuddin Hamza Shah |
E701358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bengal Sultanate ruler |
C48972
|
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: Bengal Sultanate ruler Context triple: [Saifuddin Hamza Shah, instanceOf, Bengal Sultanate ruler]
-
A.
Sayyid dynasty ruler
A Sayyid dynasty ruler is a sovereign from the Sayyid lineage who governed parts of northern India during the early 15th century, claiming descent from the Prophet Muhammad and ruling primarily from Delhi.
-
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.
Kalhora dynasty ruler
A Kalhora dynasty ruler is a sovereign from the Kalhora family who governed Sindh (in present-day Pakistan) between the early 18th and late 18th centuries, overseeing its political, economic, and cultural affairs.
-
D.
medieval Indian ruler
chosen
A medieval Indian ruler is a sovereign who governed a region of the Indian subcontinent between roughly the 8th and 16th centuries, exercising political, military, and cultural authority within a dynastic or imperial framework.
-
E.
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.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:24 p.m.