Triple

T3507686
Position Surface form Disambiguated ID Type / Status
Subject Shahanshah of Persia E74116 entity
Predicate hasFemaleEquivalent P1613 FINISHED
Object Shahbanu of Persia E342417 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: Shahbanu of Persia | Statement: [Shahanshah of Persia, hasFemaleEquivalent, Shahbanu of Persia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shahbanu of Persia
Context triple: [Shahanshah of Persia, hasFemaleEquivalent, Shahbanu of Persia]
  • A. 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.
  • B. Shah Khanum
    Shah Khanum was the grandmother of Siraj ud-Daulah, the last independent Nawab of Bengal in the mid-18th century.
  • C. Roshanak
    Roshanak is an ancient Persian female given name, often associated with Roxana, the wife of Alexander the Great.
  • D. Khanum chosen
    Khanum is a historical Turkic and Mongol honorific title used for noblewomen or female rulers, roughly equivalent to "queen" or "lady."
  • E. Shirin
    Shirin is a feminine given name of Persian origin, widely used in Iran and other Persian-influenced cultures.
  • 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc0b635c81909bc95ba2562d8f94 completed March 8, 2026, 6:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69b373e0dc7881909af631182970d132 completed March 13, 2026, 2:18 a.m.
Created at: March 8, 2026, 3:18 p.m.