Triple
T11665950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindavi Swarajya as a formal kingdom |
E277246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maratha polity |
C29654
|
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: Maratha polity Context triple: [Hindavi Swarajya as a formal kingdom, instanceOf, Maratha polity]
-
A.
post-Gupta polity
A post-Gupta polity is a regional kingdom or state formation that emerged in South Asia after the decline of the Gupta Empire, characterized by fragmented political authority, localized power centers, and evolving administrative and cultural patterns.
-
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.
Maratha fiscal levy
A Maratha fiscal levy is a tax or tribute imposed by the Maratha state on agrarian produce, trade, or territories under its influence, serving as a key instrument of revenue extraction and political control.
-
D.
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.
-
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. 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.