Triple
T7164511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Chalukya dynasty |
E167032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Indian royal dynasty |
C20889
|
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: South Indian royal dynasty Context triple: [Eastern Chalukya dynasty, instanceOf, South Indian royal dynasty]
-
A.
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.
-
B.
Hindu royal lineage
A Hindu royal lineage is a hereditary line of rulers and nobles within Hindu society, traditionally legitimized by sacred texts, divine ancestry, and ritual authority.
-
C.
Hindu ruler
A Hindu ruler is a sovereign or monarch who governs a territory while adhering to, promoting, or being culturally shaped by Hindu religious, social, and philosophical traditions.
-
D.
Nizam of Hyderabad
The Nizam of Hyderabad was the hereditary monarch and ruler of the princely state of Hyderabad in south-central India, known for immense wealth, semi-autonomous governance under British suzerainty, and a significant role in regional politics until the state's integration into the Indian Union in 1948.
-
E.
Rajput ruler
A Rajput ruler is a hereditary monarch or chieftain from the Rajput warrior clans of the Indian subcontinent, traditionally upholding codes of valor, honor, and patronage over their territories and subjects.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:47 p.m.