Triple
T14277777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Osman Ali Khan |
E353957
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Azam Unnisa Begum |
E1048577
|
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: Azam Unnisa Begum | Statement: [Mir Osman Ali Khan, spouse, Azam Unnisa Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Azam Unnisa Begum Context triple: [Mir Osman Ali Khan, spouse, Azam Unnisa Begum]
-
A.
Azam Unnisa Begum
chosen
Azam Unnisa Begum was a royal consort of the last Nizam of Hyderabad, Mir Osman Ali Khan.
-
B.
Lutfunnisa Begum
Lutfunnisa Begum was a consort of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
-
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.
Qudsia Begum
Qudsia Begum was a Mughal royal consort and influential matriarch best known as the mother of Emperor Akbar II.
-
E.
Shahida Rahman
Shahida Rahman is a notable individual honored as the namesake of Shahida and Waheed Rahman Hall, indicating her significant contributions or standing in her community or institution.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6583f0ec81909ebfc7a2c6351ff8 |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd326f62b4819084b1e984678991ae |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:10 a.m.