Triple
T27349658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jam Nizamuddin II |
E684320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Samma dynasty ruler |
C52744
|
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: Samma dynasty ruler Context triple: [Jam Nizamuddin II, instanceOf, Samma dynasty ruler]
-
A.
Aulikara dynasty ruler
An Aulikara dynasty ruler is a monarch from the early medieval Indian Aulikara lineage, governing regions of central India and known primarily through inscriptions and historical records.
-
B.
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.
-
C.
Habshi dynasty ruler
A Habshi dynasty ruler is a sovereign of African (often Ethiopian) origin who rose to power in the Indian subcontinent, typically through military or administrative service, and established or led a ruling house known as the Habshi dynasty.
-
D.
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.
-
E.
Arghun dynasty ruler
An Arghun dynasty ruler is a sovereign from the late medieval Turco-Mongol Arghun family who governed regions of present-day Afghanistan and Pakistan, particularly Sindh and parts of Baluchistan, often blending Persianate, Islamic, and Central Asian political traditions.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:47 a.m.