Triple
T20851249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukerchakia dynasty |
E513368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikh ruling 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 ruling dynasty Context triple: [Sukerchakia dynasty, instanceOf, Sikh ruling dynasty]
-
A.
Sikh dynasty
chosen
The Sikh dynasty refers to the ruling lineage and political establishment founded by Maharaja Ranjit Singh in the early 19th century, which unified much of the Punjab region into a powerful Sikh Empire before its annexation by the British.
-
B.
institution of the Sikh Empire
An institution of the Sikh Empire is an organized political, military, religious, or administrative body established under Sikh rule (c. 1799–1849) to govern, manage resources, uphold law, or promote Sikh cultural and spiritual life.
-
C.
Sikh warrior clan
A Sikh warrior clan is a traditional martial community within Sikhism, historically dedicated to defending the faith and protecting the oppressed through a code of honor, bravery, and spiritual discipline.
-
D.
ruling dynasty of North India
A ruling dynasty of North India is a hereditary line of monarchs or sovereign families that exercised political authority, controlled territory, and shaped the region’s cultural, social, and economic life over successive generations.
-
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.
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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:43 p.m.