Triple
T26586089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shashanka |
E667213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bengal ruler |
C8916
|
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: Bengal ruler Context triple: [Shashanka, instanceOf, Bengal ruler]
-
A.
Indian princely ruler
An Indian princely ruler is a hereditary monarch or sovereign of a semi-autonomous princely state in the Indian subcontinent who exercised varying degrees of internal authority under overarching imperial or colonial powers.
-
B.
ruler of Mysore
A ruler of Mysore is the sovereign authority who governed the Kingdom of Mysore, overseeing its political, military, economic, and cultural affairs during their reign.
-
C.
Hindu ruler
chosen
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.
Sultan of Mysore
The Sultan of Mysore was the hereditary Muslim monarch who ruled the Kingdom of Mysore in southern India, most notably under Hyder Ali and his son Tipu Sultan during the 18th century.
-
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.
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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:05 a.m.