Triple

T10062059
Position Surface form Disambiguated ID Type / Status
Subject Khentkaus I E213014 entity
Predicate child P120 FINISHED
Object Sahure (possible) E52420 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: Sahure (possible) | Statement: [Khentkaus I, child, Sahure (possible)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sahure (possible)
Context triple: [Khentkaus I, child, Sahure (possible)]
  • A. Sahure chosen
    Sahure was a pharaoh of Egypt’s Fifth Dynasty, best known for his pyramid complex at Abusir and for overseeing a period of prosperous trade and artistic development in the Old Kingdom.
  • B. Sobekkare
    Sobekkare is the throne name (praenomen) of Sobekneferu, a queen who ruled as a pharaoh of ancient Egypt at the end of the Twelfth Dynasty.
  • C. Sekhemkare
    Sekhemkare was an ancient Egyptian prince of the 4th Dynasty, known as a son of Pharaoh Khafre and holder of high administrative and priestly offices.
  • D. Men-nefer
    Men-nefer is the ancient Egyptian name for the city later known as Memphis, a major political and religious center near modern Cairo.
  • E. Sekhemkheperre
    Sekhemkheperre is the throne name (prenomen) of the ancient Egyptian pharaoh Osorkon I of the 22nd Dynasty.
  • 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_69ca83977128819084084eb7d1d8c52a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcfd3c6bc8190a21ed3566f9c08d1 completed April 2, 2026, 2:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d317367204819097d3ed6a72a0f8b5 completed April 6, 2026, 2:15 a.m.
Created at: March 30, 2026, 8:58 p.m.