Triple
T37859630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alif Khan |
E944288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal military commander |
C13577
|
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: Mughal military commander Context triple: [Alif Khan, instanceOf, Mughal military commander]
-
A.
Mughal official
chosen
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.
-
B.
Persian military commander
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
C.
Mongol military commander
A Mongol military commander is a high-ranking leader responsible for organizing, directing, and coordinating Mongol forces in campaigns and battles to achieve strategic and tactical objectives.
-
D.
Maratha general
A Maratha general is a high-ranking military leader in the Maratha Empire responsible for planning and commanding campaigns, managing troops, and executing the strategic objectives of Maratha rulers.
-
E.
Islamic-era military person
An Islamic-era military person is an individual who served in the armed forces of a Muslim-ruled polity during the historical periods of Islamic governance, participating in warfare, defense, or military administration.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.