Triple
T36991943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turk Shahi dynasty |
E915126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu-influenced polity |
C63682
|
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: Hindu-influenced polity Context triple: [Turk Shahi dynasty, instanceOf, Hindu-influenced polity]
-
A.
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.
-
B.
Indo-Aryan polity
An Indo-Aryan polity is a socio-political organization historically rooted in Indo-Aryan-speaking communities, typically characterized by hierarchical governance, kinship-based authority, and cultural norms derived from Vedic and later Indic traditions.
-
C.
Hindu-Buddhist kingdom
A Hindu-Buddhist kingdom is a premodern polity in South and Southeast Asia whose political authority, social order, and cultural life were shaped by a syncretic blend of Hindu and Buddhist religious, philosophical, and artistic traditions.
-
D.
Sangam-age polity
A Sangam-age polity is a socio-political entity of early historic South India characterized by chieftain-led territories, kin-based authority, and networks of warfare, tribute, and trade as reflected in Sangam literature.
-
E.
ancient Indian political concept
An ancient Indian political concept refers to the traditional ideas, institutions, and theories of governance, statecraft, and power articulated in classical Indian texts and practices, such as those found in the Arthashastra and Dharmashastra.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.