Triple

T6845597
Position Surface form Disambiguated ID Type / Status
Subject Djer E157885 entity
Predicate hasRoyalTitle P44258 FINISHED
Object Horus-king E81542 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 | Statement: [Djer, hasRoyalTitle, Horus-king]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus-king
Context triple: [Djer, hasRoyalTitle, Horus-king]
  • A. Horus
    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.
  • B. 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.
  • C. Setnakhte
    Setnakhte was the founding pharaoh of ancient Egypt’s Twentieth Dynasty, known for restoring stability after the turbulent late Nineteenth Dynasty.
  • D. Sekhemti
    Sekhemti is the ancient Egyptian Double Crown symbolizing the unified rule over Upper and Lower Egypt.
  • E. Pharaoh chosen
    Pharaoh is the title used for the ancient kings of Egypt, who ruled as powerful monarchs and were often regarded as divine or semi-divine figures.
  • 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_69c6882ed4c081909dc465a7cf8838be completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d7cbe4488190b41ddf953f12f55f completed March 27, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72fc42e688190baa8413883e5506c completed March 28, 2026, 1:32 a.m.
Created at: March 27, 2026, 2:19 p.m.