Triple
T13917102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoshbagh |
E334649
|
entity |
| Predicate | burialPlaceOf |
P196
|
FINISHED |
| Object | Lutfunnisa Begum |
E66482
|
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: Lutfunnisa Begum | Statement: [Khoshbagh, burialPlaceOf, Lutfunnisa Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lutfunnisa Begum Context triple: [Khoshbagh, burialPlaceOf, Lutfunnisa Begum]
-
A.
Lutfunnisa Begum
chosen
Lutfunnisa Begum was a consort of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
-
B.
Qudsia Begum
Qudsia Begum was a Mughal royal consort and influential matriarch best known as the mother of Emperor Akbar II.
-
C.
Maryam Begum
Maryam Begum was a Safavid royal woman best known as the mother of Shah Sultan Husayn, the last Safavid ruler of Iran.
-
D.
Dildar Begum
Dildar Begum was a consort of the Mughal emperor Babur and the mother of his son Hindal Mirza.
-
E.
Azam Unnisa Begum
Azam Unnisa Begum was a royal consort of the last Nizam of Hyderabad, Mir Osman Ali Khan.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de272753e48190bc609482635280ff |
completed | April 14, 2026, 11:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce7a1c388190a57dfdbbb732bbcb |
completed | May 3, 2026, 10:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.