Triple

T10448522
Position Surface form Disambiguated ID Type / Status
Subject Neferhetepes II E246354 entity
Predicate relative P37 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: [Neferhetepes II, relative, Userkaf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Userkaf
Context triple: [Neferhetepes II, relative, 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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fe083cd881909d2d8ad75d1d94cb completed April 7, 2026, 12:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69d8dc43e53081909e14cfe295d17cb2 completed April 10, 2026, 11:17 a.m.
Created at: April 6, 2026, 12:16 p.m.