Triple
T685975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humayun's Tomb |
E13283
|
entity |
| Predicate | patron |
P2320
|
FINISHED |
| Object | Bega 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: Bega Begum | Statement: [Humayun's Tomb, patron, Bega Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bega Begum Context triple: [Humayun's Tomb, patron, Bega Begum]
-
A.
Dildar Begum
Dildar Begum was a consort of the Mughal emperor Babur and the mother of his son Hindal Mirza.
-
B.
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.
-
C.
Hamida Banu Begum
Hamida Banu Begum was a 16th-century Mughal empress and the wife of Emperor Humayun, best known as the mother of Emperor Akbar and a significant figure in the early Mughal court.
-
D.
Sahiba Banu Begum
Sahiba Banu Begum was a Mughal princess and consort associated with the imperial family during the reign of Emperor Jahangir.
-
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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0924dec8190bbbd2bb244f85211 |
completed | March 1, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a64a53c068819089e66347da55710b |
completed | March 3, 2026, 2:41 a.m. |
Created at: March 1, 2026, 7:36 p.m.