Triple

T2806586
Position Surface form Disambiguated ID Type / Status
Subject Kubban E54066 entity
Predicate cultCenterOf P13725 FINISHED
Object Horus of Kubban E9419 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 of Kubban | Statement: [Kubban, cultCenterOf, Horus of Kubban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus of Kubban
Context triple: [Kubban, cultCenterOf, Horus of Kubban]
  • A. Horus of Kubban chosen
    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
    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. 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.
  • D. Sutekh
    Sutekh is an alternative name for the ancient Egyptian god Set, associated with chaos, storms, and disorder.
  • E. Hordjedef
    Hordjedef was an ancient Egyptian prince of the 4th Dynasty, known from Old Kingdom texts as a royal son and a sage associated with wisdom literature.
  • 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_69ab49dcee188190b5c6eca9ae9e3469 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde165a448190aa2728ec074daf88 completed March 7, 2026, 8:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1f856ad508190a92d9e9decc68c58 completed March 11, 2026, 11:18 p.m.
Created at: March 6, 2026, 9:59 p.m.