Triple

T20446618
Position Surface form Disambiguated ID Type / Status
Subject Izz al-Din Kaykaus I E501532 entity
Predicate mother P120 FINISHED
Object Ayşe Hatun 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: Ayşe Hatun | Statement: [Izz al-Din Kaykaus I, mother, Ayşe Hatun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ayşe Hatun
Context triple: [Izz al-Din Kaykaus I, mother, Ayşe Hatun]
  • A. Ayşe Hatun chosen
    Ayşe Hatun was a Seljuk noblewoman known primarily as a consort of Sultan Kilij Arslan I of the Sultanate of Rum.
  • B. Hüma Hatun
    Hüma Hatun was a consort of Ottoman Sultan Murad II and the mother of Mehmed II, the conqueror of Constantinople.
  • C. Emine Hatun
    Emine Hatun was an Ottoman consort known primarily as the wife of Sultan Mehmed I and the mother of Sultan Murad II.
  • D. Nilüfer Hatun
    Nilüfer Hatun was a 14th-century Ottoman consort and influential Valide Hatun, traditionally regarded as the wife of Orhan and mother of Sultan Murad I.
  • E. Hatice Hatun
    Hatice Hatun was an Ottoman consort known primarily as one of the wives of Sultan Murad II in the 15th century.
  • 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_69e0b4ac0a1c81908845d0f8a56abce8 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e68cfe57a8819094bd3d324bd567f5 completed April 20, 2026, 8:30 p.m.
Created at: April 16, 2026, 11:32 a.m.