Triple

T16407342
Position Surface form Disambiguated ID Type / Status
Subject Setnakhte E398467 entity
Predicate title P38 FINISHED
Object Son of Ra E131120 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: Son of Ra | Statement: [Setnakhte, title, Son of Ra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Son of Ra
Context triple: [Setnakhte, title, Son of Ra]
  • A. Son of Ra chosen
    Son of Ra is an ancient Egyptian royal epithet signifying a pharaoh’s divine filiation with the sun god Ra and his legitimized right to rule.
  • B. Re-Atum
    Re-Atum is a composite form of the ancient Egyptian sun god that unites Ra’s midday solar power with Atum’s role as the primordial creator and evening sun.
  • C. Eye of Ra
    The Eye of Ra is an ancient Egyptian symbol and deity representing the sun god Ra’s protective, vengeful, and all-seeing power, often personified by goddesses such as Wadjet.
  • D. Beloved of Re
    Beloved of Re is an ancient Egyptian theophoric name expressing devotion to the sun god Ra, commonly borne by high-ranking officials and priests.
  • E. Chosen of Set
    Chosen of Set is a dark, supernatural champion of the Egyptian god Set, marked by a cursed power and destined to serve as his earthly vessel.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d36b808190b6b8c412ae0d2faa completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00457d9f4081908a5f28eeafc44695 completed May 10, 2026, 8:44 a.m.
Created at: April 10, 2026, 5:09 a.m.