Triple
T28023237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suri Empire |
E707744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North 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: North Indian dynasty Context triple: [Suri Empire, instanceOf, North Indian dynasty]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:11 p.m.