Triple
T34699620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratan Singh I |
E1000329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Medieval Indian ruler |
C48972
|
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: Medieval Indian ruler Context triple: [Ratan Singh I, instanceOf, Medieval Indian ruler]
-
A.
medieval Indian ruler
chosen
A medieval Indian ruler is a sovereign who governed a region of the Indian subcontinent between roughly the 8th and 16th centuries, exercising political, military, and cultural authority within a dynastic or imperial framework.
-
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.
ancient Indian ruler
An ancient Indian ruler is a sovereign who governed a region of the Indian subcontinent in antiquity, exercising political, military, and often religious authority over their domain.
-
D.
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.
-
E.
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.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.