Triple
T7602268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhtiyar Khalji |
E180010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | general of the Delhi Sultanate |
C13968
|
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: general of the Delhi Sultanate Context triple: [Bakhtiyar Khalji, instanceOf, general of the Delhi Sultanate]
-
A.
member of the Khalji dynasty
chosen
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.
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.
-
C.
Mughal official
A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
-
D.
Nawab
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
-
E.
subah of the Mughal Empire
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:54 p.m.