Triple
T17819671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shivaji II |
E444943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Bhonsle dynasty |
C39182
|
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: member of the Bhonsle dynasty Context triple: [Shivaji II, instanceOf, member of the Bhonsle dynasty]
-
A.
Asaf Jahi dynasty member
A member of the Asaf Jahi dynasty is an individual belonging to the royal family that ruled the princely state of Hyderabad in India from the early 18th to the mid-20th century.
-
B.
member of the Adil Shahi dynasty
A member of the Adil Shahi dynasty is an individual belonging to the Turkic-origin royal family that ruled the Bijapur Sultanate in the Deccan region of India from the late 15th to the late 17th century.
-
C.
member of the Mughal dynasty
A member of the Mughal dynasty is an individual belonging by birth or marriage to the imperial Timurid-origin ruling family that governed large parts of the Indian subcontinent from the early 16th to the mid-19th century.
-
D.
member of the Lodi dynasty
A member of the Lodi dynasty is an individual belonging to the Afghan-origin ruling family that controlled the Delhi Sultanate in northern India during the late 15th and early 16th centuries.
-
E.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:15 a.m.