Triple
T3848075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bega Begum |
E85221
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Haji Begum |
E86202
|
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: Haji Begum | Statement: [Bega Begum, title, Haji Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haji Begum Context triple: [Bega Begum, title, Haji Begum]
-
A.
Haji Begum
chosen
Haji Begum was a Mughal empress and chief consort of Emperor Humayun, best known for overseeing the construction of his grand mausoleum in Delhi.
-
B.
Dildar Begum
Dildar Begum was a consort of the Mughal emperor Babur and the mother of his son Hindal Mirza.
-
C.
Mahlara Begum
Mahlara Begum was a consort of the Mughal emperor Akbar II during the late Mughal period in India.
-
D.
Rifa’at Begum
Rifa’at Begum was the wife of Iskander Mirza, the first President of Pakistan, and thus served as Pakistan’s First Lady during his tenure.
-
E.
Lutfunnisa Begum
Lutfunnisa Begum was a consort of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcc8a0481909c35161336bdfbf9 |
completed | March 9, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5db641e608190b9d5b190468c501f |
completed | March 14, 2026, 10:04 p.m. |
Created at: March 9, 2026, 3:19 p.m.