Triple

T10759003
Position Surface form Disambiguated ID Type / Status
Subject Userkare E253774 entity
Predicate title P38 FINISHED
Object Horus-king (probable) E58877 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: Horus-king (probable) | Statement: [Userkare, title, Horus-king (probable)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus-king (probable)
Context triple: [Userkare, title, Horus-king (probable)]
  • A. Horus of Kubban
    Horus of Kubban is a local form of the ancient Egyptian god Horus venerated in the Nubian region near Kubban, associated with kingship and protection.
  • B. Horus chosen
    Horus is a major ancient Egyptian sky and kingship god, often depicted as a falcon or falcon-headed man and closely associated with divine rulership and protection.
  • C. Sekhemib
    Sekhemib was the Horus name of Psamtik II, a pharaoh of Egypt’s 26th Dynasty known for his military campaigns and monumental building projects.
  • D. Sekhemre
    Sekhemre was an ancient Egyptian royal figure, likely a prince or king associated with the lineage of Pharaoh Menkaura of the Fourth Dynasty.
  • E. Sekhemti
    Sekhemti is the ancient Egyptian Double Crown symbolizing the unified rule over Upper and Lower Egypt.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d72ea21c5081908babc049d0330a75 completed April 9, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69dbdbc3780c819092337924e2ae90f8 completed April 12, 2026, 5:52 p.m.
Created at: April 8, 2026, 9:16 p.m.