Triple

T1547037
Position Surface form Disambiguated ID Type / Status
Subject Khafre E33000 entity
Predicate royalTitle P17683 FINISHED
Object Horus-king 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 | Statement: [Khafre, royalTitle, Horus-king]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus-king
Context triple: [Khafre, royalTitle, Horus-king]
  • A. 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.
  • 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. Pharaoh
    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.
  • D. Khnum
    Khnum is an ancient Egyptian ram-headed god associated with the Nile’s inundation, creation, and the molding of human beings on a potter’s wheel.
  • E. Hor-Aha
    Hor-Aha was an early dynastic Egyptian pharaoh, traditionally regarded as one of the first rulers of a unified Egypt and a founder of the First Dynasty.
  • 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_69a885ee6db8819099502bc5ce8af881 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abb20dd5a88190b3d6e6f0004fe9b4 completed March 7, 2026, 5:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad68079e448190b71c2cd194abeb86 completed March 8, 2026, 12:13 p.m.
Created at: March 4, 2026, 7:26 p.m.