Triple
T26404150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chikka Devaraja Wadiyar |
E663784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wadiyar dynasty ruler |
C51523
|
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: Wadiyar dynasty ruler Context triple: [Chikka Devaraja Wadiyar, instanceOf, Wadiyar dynasty ruler]
-
A.
Sayyid dynasty ruler
A Sayyid dynasty ruler is a sovereign from the Sayyid lineage who governed parts of northern India during the early 15th century, claiming descent from the Prophet Muhammad and ruling primarily from Delhi.
-
B.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
C.
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.
-
D.
Madurai Nayak dynasty ruler
A Madurai Nayak dynasty ruler is a sovereign or co-sovereign from the Nayak lineage who governed the Madurai region of South India between the 16th and 18th centuries, overseeing its political administration, military affairs, and cultural patronage.
-
E.
Kakatiya ruler
A Kakatiya ruler is a monarch from the medieval Kakatiya dynasty of South India, known for consolidating regional power, promoting trade and irrigation, and patronizing distinctive temple architecture and Telugu culture.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:33 p.m.