Triple

T8579028
Position Surface form Disambiguated ID Type / Status
Subject Amenhotep III E203120 entity
Predicate child P120 FINISHED
Object Sitamun E744221 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: Sitamun | Statement: [Amenhotep III, child, Sitamun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sitamun
Context triple: [Amenhotep III, child, Sitamun]
  • A. Sitamun chosen
    Sitamun was an ancient Egyptian princess of the 18th Dynasty, likely a daughter of Amenhotep III and Queen Tiye, who was elevated to the status of Great Royal Wife during her father's reign.
  • B. Sasima
    Sasima was an obscure town in ancient Cappadocia, best known as the short-lived and reluctant episcopal see of Gregory of Nazianzus in the 4th century.
  • C. Saklatvala
    Saklatvala is an Indian-origin surname most notably associated with Shapurji Saklatvala, a pioneering communist and one of the first British MPs of Indian descent.
  • D. Sambir
    Sambir is a small historic city in western Ukraine known for its medieval roots and location within the Lviv Oblast.
  • E. Kamsa
    Kamsa is a tyrannical king in Hindu mythology, best known as the evil uncle and nemesis of Lord Krishna.
  • 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_69ca8328ebe481909a8c038fa79959b4 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbea9a0708819084cb8b8d84017864 completed March 31, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea89550f481908a7ed45303b71731 completed April 2, 2026, 5:34 p.m.
Created at: March 30, 2026, 6:22 p.m.