Triple
T29610904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinsinwar Jat dynasty |
E754716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jat dynasty |
C40415
|
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: Jat dynasty Context triple: [Sinsinwar Jat dynasty, instanceOf, Jat dynasty]
-
A.
Sikh dynasty
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.
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.
-
C.
Jat clan
chosen
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.
-
D.
Puranic dynasty
A Puranic dynasty is a lineage of rulers or royal families described in the Hindu Puranas, often blending mythological, legendary, and historical elements to trace the succession of kings across cosmic ages.
-
E.
Magadha dynasty
The Magadha dynasty refers to the succession of ruling houses that controlled the ancient Indian kingdom of Magadha, a powerful political and cultural center in the eastern Gangetic plain that laid the foundation for major empires like the Maurya and Gupta.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:28 p.m.