Triple
T11277588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipu Sultan |
E266975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sultan of Mysore |
C29480
|
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: Sultan of Mysore Context triple: [Tipu Sultan, instanceOf, Sultan of Mysore]
-
A.
Maharaja
A Maharaja is a hereditary Indian monarch or high-ranking noble, traditionally ruling over a princely state with significant political, military, and cultural authority.
-
B.
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.
-
C.
Nawab
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
-
D.
ruler of Indore
The ruler of Indore is the sovereign or governing authority who historically held political power and administrative control over the princely state or region of Indore.
-
E.
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.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.