Triple

T17970828
Position Surface form Disambiguated ID Type / Status
Subject Seqenenre Tao E449334 entity
Predicate successor P78 FINISHED
Object Kamose 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: Kamose | Statement: [Seqenenre Tao, successor, Kamose]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kamose
Context triple: [Seqenenre Tao, successor, Kamose]
  • A. Kamose chosen
    Kamose was a late-17th Dynasty pharaoh known for his military campaigns against the Hyksos that helped pave the way for the reunification of ancient Egypt.
  • B. Siptah
    Siptah was a late 19th Dynasty pharaoh of ancient Egypt who ruled briefly during a turbulent period marked by political instability and power struggles.
  • C. Setnakhte
    Setnakhte was the founding pharaoh of ancient Egypt’s Twentieth Dynasty, known for restoring stability after the turbulent late Nineteenth Dynasty.
  • D. Nekheb
    Nekheb was an ancient Egyptian city in Upper Egypt, closely associated with the vulture goddess Nekhbet and serving as an important religious and political center.
  • E. Kha-sekhemui
    Kha-sekhemui, better known as Khasekhemwy, was a pharaoh of Egypt’s Second Dynasty noted for reuniting Upper and Lower Egypt and for his distinctive monuments at Hierakonpolis and Abydos.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b1fa67c48190936f20cea45e4599 completed April 19, 2026, 10:44 a.m.
Created at: April 10, 2026, 10:22 a.m.