Triple
T23170674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shishunaga dynasty |
E578850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Magadha dynasty |
C47335
|
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: Magadha dynasty Context triple: [Shishunaga dynasty, instanceOf, Magadha 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.
Indo-Scythian dynasties
Indo-Scythian dynasties were ancient ruling houses of Scythian origin that established kingdoms in parts of northwestern and western South Asia between roughly the 2nd century BCE and the 4th century CE, blending Central Asian nomadic traditions with Hellenistic and Indian cultural and political forms.
-
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.
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.
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. 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:03 p.m.