Triple

T11485636
Position Surface form Disambiguated ID Type / Status
Subject Neferirkare Kakai E272267 entity
Predicate father P120 FINISHED
Object Userkaf E49148 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: Userkaf | Statement: [Neferirkare Kakai, father, Userkaf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Userkaf
Context triple: [Neferirkare Kakai, father, Userkaf]
  • A. Userkaf chosen
    Userkaf was a pharaoh of Egypt’s Fifth Dynasty, best known for initiating the construction of sun temples and helping establish the prominence of the solar cult of Ra.
  • B. Userkare
    Userkare was a short-reigning pharaoh of Egypt’s Sixth Dynasty, known primarily from sparse archaeological and textual evidence that leaves many details of his rule uncertain.
  • C. Usery
    Usery is a surname most notably associated with William J. Usery Jr., a prominent American labor union activist and U.S. Secretary of Labor.
  • D. Kuser
    Kuser is a surname associated with an American family notable in New Jersey politics, business, and public life in the late 19th and early 20th centuries.
  • E. Useriner See
    Useriner See is a lake in northeastern Germany, situated within the Mecklenburg Lake District and known for its natural scenery and recreational opportunities.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85a1ea00c8190b42cdc13a6bc61c3 completed April 10, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69e60451a89081909f9534fee6cb809f completed April 20, 2026, 10:47 a.m.
Created at: April 8, 2026, 9:36 p.m.