Triple

T19143539
Position Surface form Disambiguated ID Type / Status
Subject Begums of Bhopal E468617 entity
Predicate hasMember P10 FINISHED
Object Qudsia Begum NE NERFINISHED

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: Qudsia Begum | Statement: [Begums of Bhopal, hasMember, Qudsia Begum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qudsia Begum
Context triple: [Begums of Bhopal, hasMember, Qudsia Begum]
  • A. Qudsia Begum chosen
    Qudsia Begum was a Mughal royal consort and influential matriarch best known as the mother of Emperor Akbar II.
  • B. Maryam Begum
    Maryam Begum was a Safavid royal woman best known as the mother of Shah Sultan Husayn, the last Safavid ruler of Iran.
  • C. Lutfunnisa Begum
    Lutfunnisa Begum was a consort of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
  • D. Wafa Begum
    Wafa Begum was a queen consort of the Durrani Empire as the wife of Afghan ruler Shuja Shah Durrani.
  • E. Dildar Begum
    Dildar Begum was a consort of the Mughal emperor Babur and the mother of his son Hindal Mirza.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd0796a48190b34ce4cd9d3f3be5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e977fa208190aa8cafd0966599c6 completed April 20, 2026, 8:53 a.m.
Created at: April 10, 2026, 12:05 p.m.