Triple
T14950023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rukn ud-Din Firuz |
E372767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Mamluk dynasty of Delhi |
C35311
|
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 Mamluk dynasty of Delhi Context triple: [Rukn ud-Din Firuz, instanceOf, member of the Mamluk dynasty of Delhi]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
member of the Ottoman dynasty
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:39 a.m.