Triple
T3465385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khurram |
E73123
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Izz-un-Nissa Begum |
E147119
|
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: Izz-un-Nissa Begum | Statement: [Khurram, spouse, Izz-un-Nissa Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Izz-un-Nissa Begum Context triple: [Khurram, spouse, Izz-un-Nissa Begum]
-
A.
Izz-un-Nissa Begum
chosen
Izz-un-Nissa Begum was a Mughal princess and one of Emperor Shah Jahan’s wives, known for her high rank and influence within the imperial harem.
-
B.
Dilras Banu Begum
Dilras Banu Begum was a 17th-century Mughal princess and the chief consort of Emperor Aurangzeb, remembered as the mother of several of his children and for the grand mausoleum Bibi Ka Maqbara built in her memory.
-
C.
Maham Begum
Maham Begum was a chief consort of the Mughal emperor Babur and the mother of his successor, Humayun.
-
D.
Lutf-un-nisa Begum
Lutf-un-nisa Begum was a Mughal-era noblewoman whose name appears in historical records of the imperial court.
-
E.
Jamil-ud-Din Begum
Jamil-ud-Din Begum was a Mughal royal consort and the mother of the 18th-century Mughal emperor Shah Alam II.
- 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_69b4e4d1c7188190b0f98fdc51e6684a |
completed | March 14, 2026, 4:32 a.m. |
Created at: March 8, 2026, 3:17 p.m.