Triple

T14757869
Position Surface form Disambiguated ID Type / Status
Subject Alivardi Khan E346777 entity
Predicate mother P120 FINISHED
Object Shah Khanum E66137 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: Shah Khanum | Statement: [Alivardi Khan, mother, Shah Khanum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shah Khanum
Context triple: [Alivardi Khan, mother, Shah Khanum]
  • A. Shah Khanum chosen
    Shah Khanum was the grandmother of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
  • B. Dilaram Khanum
    Dilaram Khanum was a Safavid royal consort and the mother of Shah Safi I of Persia in the 17th century.
  • C. Tajlu Khanum
    Tajlu Khanum was a prominent Safavid royal consort and queen mother, best known as the influential mother of Shah Tahmasp I of Iran.
  • D. Kandahari Begum
    Kandahari Begum was a Mughal princess and the first wife of Emperor Shah Jahan, known for her Timurid lineage and political significance in the Mughal court.
  • E. Saray Mulk Khanum
    Saray Mulk Khanum was a prominent 14th-century Central Asian noblewoman and chief consort of the conqueror Timur, noted for her political influence and patronage of architecture in the Timurid court.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7f0f5a48190af008352c26574d7 completed April 14, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe24afff788190ab4925ead7ce90d2 completed May 8, 2026, 6 p.m.
Created at: April 10, 2026, 1:30 a.m.