Triple

T3716487
Position Surface form Disambiguated ID Type / Status
Subject Pharaoh E81542 entity
Predicate linkedToDeity P7649 FINISHED
Object Horus 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 | Statement: [Pharaoh, linkedToDeity, Horus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus
Context triple: [Pharaoh, linkedToDeity, Horus]
  • 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. Khonsu
    Khonsu is an ancient Egyptian lunar god associated with time, healing, and protection, often worshipped as the son of Amun and Mut.
  • D. Sobek
    Sobek is an ancient Egyptian crocodile-headed god associated with the Nile, military power, and protection.
  • E. Sutekh
    Sutekh is an alternative name for the ancient Egyptian god Set, associated with chaos, storms, and disorder.
  • 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_69ad8b1a81588190b3f27a5483bb610e completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc9cf77dc819098979094172d82d1 completed March 8, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4fb074a9881909afec640a5a208c6 completed March 14, 2026, 6:07 a.m.
Created at: March 8, 2026, 3:33 p.m.