Triple

T15106988
Position Surface form Disambiguated ID Type / Status
Subject Mehr-un-Nissa E360811 entity
Predicate title P38 FINISHED
Object Padshah Begum E364055 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: Padshah Begum | Statement: [Mehr-un-Nissa, title, Padshah Begum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Padshah Begum
Context triple: [Mehr-un-Nissa, title, Padshah Begum]
  • A. Padshah Begum chosen
    Padshah Begum was the prestigious imperial title historically borne by the chief consort or foremost woman of the Mughal court, signifying her status as empress and leading lady of the empire.
  • B. Sultan Begum
    Sultan Begum is a historical female figure from the Mughal era, known primarily as a royal consort within the early Mughal imperial family.
  • C. Badshah Begum
    Badshah Begum was a prominent Mughal empress and influential royal consort in 18th-century India.
  • D. Shah Begum
    Shah Begum was a Timurid-era noblewoman known as the daughter of Qutlugh Nigar Khanum and a member of the Mughal imperial family.
  • E. Sultanam Begum
    Sultanam Begum was a Mughal noblewoman known primarily as the mother of Ruqaiya Sultan Begum, chief consort of the emperor Akbar.
  • 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_69d85a0491ec8190830960be8fafb994 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0058af8988190977d998f85893836 completed April 15, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff8754ef408190be0e4ea5c35cf000 completed May 9, 2026, 7:13 p.m.
Created at: April 10, 2026, 3:05 a.m.