Triple
T19018245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jahan Shah |
E465413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Mughal dynasty |
C33485
|
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 Mughal dynasty Context triple: [Jahan Shah, instanceOf, member of Mughal dynasty]
-
A.
member of the Mughal dynasty
chosen
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.
-
B.
member of the Khalji dynasty
A member of the Khalji dynasty is an individual belonging to the Turkic-origin ruling family that controlled the Delhi Sultanate in northern India during the late 13th and early 14th centuries.
-
C.
member of the Mamluk dynasty of Delhi
A member of the Mamluk dynasty of Delhi is an individual belonging to the first ruling dynasty of the Delhi Sultanate (c. 1206–1290), originally composed largely of Turkic slave-soldiers who rose to power and established Muslim rule in northern India.
-
D.
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.
-
E.
member of the Tughlaq dynasty
A member of the Tughlaq dynasty is an individual belonging to the medieval Muslim ruling family that governed the Delhi Sultanate in northern India during the 14th century, known for ambitious reforms, extensive territorial control, and periods of political instability.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.