Triple
T20851250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukerchakia dynasty |
E513368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Punjabi royal house |
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: Punjabi royal house Context triple: [Sukerchakia dynasty, instanceOf, Punjabi royal house]
-
A.
Indian royal dynasty
An Indian royal dynasty is a hereditary ruling family or lineage that governed a specific region or kingdom in the Indian subcontinent, often characterized by distinct cultural, political, and architectural legacies.
-
B.
Jat clan
A Jat clan is a kinship-based social group within the broader Jat community, traditionally organized by common ancestry, shared lineage, and customary practices, often influencing identity, marriage, and social status in North Indian and Pakistani societies.
-
C.
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.
-
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.
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.
- 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.