Triple
T35910111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyan Chand |
E1038582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Chand dynasty |
C65438
|
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 Chand dynasty Context triple: [Kalyan Chand, instanceOf, member of Chand dynasty]
-
A.
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.
-
B.
Sailendra dynasty member
A Sailendra dynasty member is an individual belonging to the influential Buddhist ruling family that dominated parts of Java and Sumatra in Southeast Asia between the 8th and 9th centuries, known for monumental architecture like Borobudur and extensive maritime trade.
-
C.
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.
-
D.
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.
-
E.
Chandela ruler
A Chandela ruler is a monarch from the medieval Indian Chandela dynasty, known for governing central Indian regions like Bundelkhand and commissioning monumental Hindu and Jain temples such as those at Khajuraho.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.