Triple

T22044443
Position Surface form Disambiguated ID Type / Status
Subject Sekhemti E544723 entity
Predicate hasComponent P35 FINISHED
Object Deshret 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: Deshret | Statement: [Sekhemti, hasComponent, Deshret]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Deshret
Context triple: [Sekhemti, hasComponent, Deshret]
  • A. Deshret chosen
    Deshret is the ancient Egyptian Red Crown symbolizing the pharaonic authority and land of Lower Egypt.
  • B. Djer
    Djer was an early pharaoh of Egypt’s First Dynasty, known from tomb remains at Abydos and later king lists as one of the earliest historical rulers of a unified Egyptian state.
  • C. Misrikh
    Misrikh is a town and municipal body in the Sitapur district of Uttar Pradesh, India, known for its local administrative and commercial significance in the region.
  • D. Sekhen
    Sekhen is an alternative name for the ancient Egyptian king Ka, an early ruler of the First Dynasty period.
  • E. Theban nome
    The Theban nome was an ancient administrative district of Upper Egypt centered on the powerful religious and political city of Thebes (Waset).
  • 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_69f1282d5bb08190849d5084962bf3a5 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.