Triple
T3662883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruqaiya Sultan Begum |
E77690
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Padshah Begum |
E364055
|
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: Padshah Begum | Statement: [Ruqaiya Sultan Begum, title, Padshah Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Padshah Begum Context triple: [Ruqaiya Sultan Begum, title, Padshah Begum]
-
A.
Padshah Begum
chosen
Padshah Begum was the prestigious imperial title historically borne by the chief consort or foremost woman of the Mughal court, signifying her status as empress and leading lady of the empire.
-
B.
Sultan Begum
Sultan Begum is a historical female figure from the Mughal era, known primarily as a royal consort within the early Mughal imperial family.
-
C.
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.
-
D.
Sultanam Begum
Sultanam Begum was a Mughal noblewoman known primarily as the mother of Ruqaiya Sultan Begum, chief consort of the emperor Akbar.
-
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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fcd910819082012b10b23860aa |
completed | March 8, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5a826850c8190b7c6853e12d09606 |
completed | March 14, 2026, 6:25 p.m. |
Created at: March 8, 2026, 3:25 p.m.