Triple
T17803105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasir-ud-Din Mahmud Shah Tughlaq |
E444484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tughlaq ruler |
C13355
|
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: Tughlaq ruler Context triple: [Nasir-ud-Din Mahmud Shah Tughlaq, instanceOf, Tughlaq ruler]
-
A.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
B.
Sayyid dynasty ruler
A Sayyid dynasty ruler is a sovereign from the Sayyid lineage who governed parts of northern India during the early 15th century, claiming descent from the Prophet Muhammad and ruling primarily from Delhi.
-
C.
member of the Tughlaq dynasty
chosen
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.
-
D.
Mongol ruler
A Mongol ruler is a sovereign leader of the Mongol people and their empire, wielding military, political, and often spiritual authority over vast, multiethnic territories.
-
E.
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.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:13 a.m.