Triple
T27330517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prabhakaravardhana |
E689785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pushyabhuti dynasty ruler |
C52731
|
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: Pushyabhuti dynasty ruler Context triple: [Prabhakaravardhana, instanceOf, Pushyabhuti dynasty ruler]
-
A.
Aulikara dynasty ruler
An Aulikara dynasty ruler is a monarch from the early medieval Indian Aulikara lineage, governing regions of central India and known primarily through inscriptions and historical records.
-
B.
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.
-
C.
Gurjara-Pratihara ruler
A Gurjara-Pratihara ruler is a monarch from the early medieval North Indian Gurjara-Pratihara dynasty, known for resisting Arab invasions and patronizing art, architecture, and regional political consolidation between the 8th and 11th centuries.
-
D.
Vemulavada Chalukya ruler
A Vemulavada Chalukya ruler is a monarch from the medieval South Indian Chalukya dynasty based at Vemulavada, known for regional governance, temple patronage, and participation in Deccan power politics.
-
E.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:37 a.m.