Triple

T13095627
Position Surface form Disambiguated ID Type / Status
Subject Djedefhor E310576 entity
Predicate relative P37 FINISHED
Object Djedefre 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: Djedefre | Statement: [Djedefhor, relative, Djedefre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Djedefre
Context triple: [Djedefhor, relative, Djedefre]
  • A. Djedefre chosen
    Djedefre was a pharaoh of Egypt’s 4th Dynasty, best known as a son and successor of Khufu and for building a pyramid complex at Abu Rawash.
  • B. Djedefhor
    Djedefhor was an ancient Egyptian prince of the 4th Dynasty, known from wisdom literature and inscriptions as a royal son and court official during the Old Kingdom.
  • C. Neferefre
    Neferefre was a short-reigning pharaoh of Egypt’s Fifth Dynasty, known primarily from his unfinished pyramid at Abusir and limited archaeological remains.
  • D. Sahure
    Sahure was a pharaoh of Egypt’s Fifth Dynasty, best known for his pyramid complex at Abusir and for overseeing a period of prosperous trade and artistic development in the Old Kingdom.
  • E. Khakheperre
    Khakheperre was the throne name of the ancient Egyptian pharaoh Senusret II of the Twelfth 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_69d806a733548190989cfd4ce981ca33 completed April 9, 2026, 8:05 p.m.
NER Named-entity recognition batch_69d9814e88a0819088418c792ce7aa57 completed April 10, 2026, 11:01 p.m.
Created at: April 9, 2026, 9:03 p.m.