Triple

T17892448
Position Surface form Disambiguated ID Type / Status
Subject Sanjar E447354 entity
Predicate spouse P13 FINISHED
Object Gawhar Khatun 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: Gawhar Khatun | Statement: [Sanjar, spouse, Gawhar Khatun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gawhar Khatun
Context triple: [Sanjar, spouse, Gawhar Khatun]
  • A. Gawhar Khatun chosen
    Gawhar Khatun was a medieval noblewoman known as the wife of Ibrahim of Ghazni, a ruler of the Ghaznavid Empire in present-day Afghanistan and surrounding regions.
  • B. Taj al-Din Khatun
    Taj al-Din Khatun was a medieval Persian noblewoman known primarily as the mother of the Seljuk ruler Sanjar.
  • C. Hamida Khatun
    Hamida Khatun was a respected early Islamic woman known primarily as the mother of Musa al-Kadhim, the seventh Shia Imam.
  • D. Qaitmish Khatun
    Qaitmish Khatun was a noblewoman of the Ilkhanate period, best known as the mother of the Mongol ruler Arghun.
  • E. Töregene Khatun
    Töregene Khatun was a powerful Mongol empress who served as regent of the Mongol Empire after Ögedei Khan’s death, playing a key role in imperial politics and succession.
  • 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49d7a855c8190b20bdbf6dcd4fd47 completed April 19, 2026, 9:16 a.m.
Created at: April 10, 2026, 10:19 a.m.