Triple
T18837332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoshang Shah |
E460697
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Mahmud Khalji |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mahmud Khalji | Statement: [Hoshang Shah, successor, Mahmud Khalji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mahmud Khalji Context triple: [Hoshang Shah, successor, Mahmud Khalji]
-
A.
Mahmud Khalji
chosen
Mahmud Khalji was a 15th-century Sultan of Malwa in central India, known for his military campaigns and conflicts with neighboring Rajput kingdoms.
-
B.
Muiz ud-Din
Muiz ud-Din was a 13th-century ruler of the Delhi Sultanate from the Mamluk (Slave) dynasty who briefly held the throne during a period of intense political instability.
-
C.
Muhammad of Ghor
Muhammad of Ghor was a 12th-century Ghurid sultan whose conquests in northern India laid the foundations for Muslim rule and the later Delhi Sultanate.
-
D.
Qutb-ul-Mulk
Qutb-ul-Mulk was the founder of the Qutb Shahi dynasty, which ruled the Golconda Sultanate in south-central India.
-
E.
Muzaffar al-Din
Muzaffar al-Din was a prominent historical figure whose legacy gave his name to the Muzaffarid dynasty in the Islamic world.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.