Triple
T26782964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sena dynasty |
E670298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Indian royal dynasty |
C30465
|
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: medieval Indian royal dynasty Context triple: [Sena dynasty, instanceOf, medieval Indian royal dynasty]
-
A.
Indian royal dynasty
chosen
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.
ruling dynasty of North India
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.
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.
-
D.
medieval Indian ruler
A medieval Indian ruler is a sovereign who governed a region of the Indian subcontinent between roughly the 8th and 16th centuries, exercising political, military, and cultural authority within a dynastic or imperial framework.
-
E.
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.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:10 a.m.