Triple
T38129006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijapur Sultanate |
E952164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Deccan kingdom |
C64104
|
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: Deccan kingdom Context triple: [Bijapur Sultanate, instanceOf, Deccan kingdom]
-
A.
South Indian kingdom
A South Indian kingdom is a historically or culturally defined political entity located in the southern part of the Indian subcontinent, characterized by distinct Dravidian languages, traditions, and regional governance.
-
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.
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.
-
D.
Hindu kingdom
A Hindu kingdom is a pre-modern or early modern polity in South Asia whose ruling dynasty, state ideology, and major institutions were grounded in Hindu religious, social, and cultural traditions.
-
E.
Maratha polity
Maratha polity refers to the decentralized, confederate political system of the Maratha Empire, characterized by a powerful but often contested central authority (the Chhatrapati and Peshwa) and semi-autonomous regional chiefs (sardars) who exercised significant military, fiscal, and administrative control.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.