Triple
T16448193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sukerchakia |
E399486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikh dynasty |
C37467
|
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: Sikh dynasty Context triple: [House of Sukerchakia, instanceOf, Sikh dynasty]
-
A.
Bengal dynasty
The Bengal dynasty refers to the succession of ruling families and political powers that governed the Bengal region (in present-day Bangladesh and eastern India) across various historical periods, shaping its cultural, economic, and political development.
-
B.
Pashtun dynasty
A Pashtun dynasty is a ruling lineage or royal house originating from the Pashtun ethnic group, historically governing territories in regions such as present-day Afghanistan, Pakistan, and northern India.
-
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.
Tamil dynasty
A Tamil dynasty is a ruling lineage originating from the Tamil-speaking regions of South India and Sri Lanka, characterized by its political authority, cultural patronage, and influence over Tamil society and history.
-
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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.