Triple
T7639643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Guptas |
E172966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-Gupta polity |
C22330
|
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: post-Gupta polity Context triple: [Later Guptas, instanceOf, post-Gupta polity]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
early modern Indian polity
Early modern Indian polity refers to the complex, regionally diverse systems of governance, authority, and political negotiation that emerged in the Indian subcontinent roughly between the 16th and 18th centuries, encompassing empires, kingdoms, and local powers interacting through warfare, diplomacy, and administration.
-
E.
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.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:57 p.m.