Triple

T22040567
Position Surface form Disambiguated ID Type / Status
Subject King Scorpion E544626 entity
Predicate successorCandidate P78 FINISHED
Object Ka (Sekhen)} 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: Ka (Sekhen)} | Statement: [King Scorpion, successorCandidate, Ka (Sekhen)}]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ka (Sekhen)}
Context triple: [King Scorpion, successorCandidate, Ka (Sekhen)}]
  • A. Sekhen chosen
    Sekhen is an alternative name for the ancient Egyptian king Ka, an early ruler of the First Dynasty period.
  • B. s-m-n-ḫ-k3-rˁ
    s-m-n-ḫ-k3-rˁ is the ancient Egyptian hieroglyphic rendering of the throne name of Pharaoh Smenkhkare, a little-known ruler of the late 18th Dynasty associated with the Amarna period.
  • C. Kaa-Khem
    Kaa-Khem is the local name for the Little Yenisei River, a tributary of the Yenisei flowing through the Tuva region of southern Siberia.
  • D. 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.
  • E. Setekh
    Setekh is an alternative transliteration of Set, the ancient Egyptian god associated with chaos, storms, deserts, and disorder.
  • 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12828fc788190a22c0e9c2372656b completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.