Triple
T26968988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamsuddin Muzaffar Shah |
E679253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habshi dynasty ruler |
C52312
|
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: Habshi dynasty ruler Context triple: [Shamsuddin Muzaffar Shah, instanceOf, Habshi dynasty ruler]
-
A.
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.
-
B.
Wadiyar dynasty ruler
A Wadiyar dynasty ruler is a monarch from the royal family that governed the Kingdom of Mysore, overseeing its political, cultural, and economic development across several centuries in southern India.
-
C.
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.
-
D.
Ashtarkhanid dynasty ruler
An Ashtarkhanid dynasty ruler is a sovereign from the Uzbek-origin Ashtarkhanid (Janid) line who governed the Khanate of Bukhara in Central Asia between the late 16th and mid-18th centuries.
-
E.
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.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:38 a.m.