Triple
T7682390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mian Ghulam Shah Kalhoro |
E174027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kalhora dynasty ruler |
C22671
|
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: Kalhora dynasty ruler Context triple: [Mian Ghulam Shah Kalhoro, instanceOf, Kalhora dynasty ruler]
-
A.
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.
-
B.
Rajput ruler
A Rajput ruler is a hereditary monarch or chieftain from the Rajput warrior clans of the Indian subcontinent, traditionally upholding codes of valor, honor, and patronage over their territories and subjects.
-
C.
Nawab
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
-
D.
Sikh prince
A Sikh prince is a male royal figure from a Sikh ruling family or lineage, traditionally responsible for leadership, protection of the community, and upholding Sikh religious and cultural values.
-
E.
member of the Durrani dynasty
A member of the Durrani dynasty is an individual belonging to the Pashtun royal lineage that ruled Afghanistan and parts of surrounding regions from the mid-18th to the 19th century, originating with Ahmad Shah Durrani.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:01 p.m.