Triple
T3465383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khurram |
E73123
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Kandahari Begum |
E145704
|
NE FINISHED |
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: Kandahari Begum | Statement: [Khurram, spouse, Kandahari Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kandahari Begum Context triple: [Khurram, spouse, Kandahari Begum]
-
A.
Kandahari Begum
chosen
Kandahari Begum was a Mughal princess and the first wife of Emperor Shah Jahan, known for her Timurid lineage and political significance in the Mughal court.
-
B.
Khanzada Begum
Khanzada Begum was a Timurid princess and elder sister of Mughal emperor Babur, noted for her political marriages and influential role in early Mughal diplomacy.
-
C.
Salima Sultan Begum
Salima Sultan Begum was a Mughal empress and influential consort in the court of Emperor Akbar, known for her political acumen and high status within the imperial harem.
-
D.
Shah Begum
Shah Begum was a Timurid-era noblewoman known as the daughter of Qutlugh Nigar Khanum and a member of the Mughal imperial family.
-
E.
Maham Begum
Maham Begum was a chief consort of the Mughal emperor Babur and the mother of his successor, Humayun.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0f2d3881908a5fa871341564ed |
completed | March 8, 2026, 6:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4daeff8c0819097e60f893e6669d5 |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:17 p.m.