Triple
T26858863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suri dynasty |
E676271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern Indian dynasty |
C22649
|
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: early modern Indian dynasty Context triple: [Suri dynasty, instanceOf, early modern Indian 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.
ruling dynasty of North India
chosen
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.
-
C.
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.
-
D.
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.
-
E.
South Indian dynasty
A South Indian dynasty is a long-standing ruling lineage or family that governed regions of southern India, shaping its political history, culture, religion, and art over successive generations.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:23 a.m.