Triple
T15735512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaf Jah VI |
E381459
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian princely ruler |
C35797
|
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: Indian princely ruler Context triple: [Asaf Jah VI, instanceOf, Indian princely ruler]
-
A.
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.
-
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.
last ruler of a princely state
The last ruler of a princely state is the final sovereign or monarch who held authority over a semi-autonomous regional kingdom or territory before its dissolution, annexation, or integration into a larger political entity.
-
D.
Rajput princely state
A Rajput princely state was a semi-autonomous, monarch-ruled territory in the Indian subcontinent governed by a Rajput dynasty under the suzerainty of larger empires such as the Mughals or the British Crown.
-
E.
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.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.