Triple

T18484383
Position Surface form Disambiguated ID Type / Status
Subject Ankhesenamun E451647 entity
Predicate relative P37 FINISHED
Object Smenkhkare 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: Smenkhkare | Statement: [Ankhesenamun, relative, Smenkhkare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Smenkhkare
Context triple: [Ankhesenamun, relative, Smenkhkare]
  • A. Smenkhkare chosen
    Smenkhkare was a little-known and short-reigning pharaoh of Egypt’s 18th Dynasty, associated with the Amarna period and the tumultuous final years of Akhenaten’s religious revolution.
  • B. Nebkheperure
    Nebkheperure is the throne name of the ancient Egyptian pharaoh Tutankhamun, used as part of his royal titulary during the 18th Dynasty.
  • C. Userkhaure-setepenre Setnakhte
    Userkhaure-setepenre Setnakhte was the founding pharaoh of Egypt’s Twentieth Dynasty, known for restoring stability after the turbulent late Nineteenth Dynasty.
  • D. Neferefre
    Neferefre was a short-reigning pharaoh of Egypt’s Fifth Dynasty, known primarily from his unfinished pyramid at Abusir and limited archaeological remains.
  • 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 (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_69d8d3855d50819097fc8561b0299dd9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e531d6502c8190af167b954bf8e989 completed April 19, 2026, 7:49 p.m.
Created at: April 10, 2026, 11:35 a.m.