Triple

T2679887
Position Surface form Disambiguated ID Type / Status
Subject Osiris myth E56548 entity
Predicate centralDeity P1194 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: [Osiris myth, centralDeity, Horus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horus
Context triple: [Osiris myth, centralDeity, 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_69ab4a4b13fc81909dfdb3f23da46832 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd9d36ea8819094ada73d86ffaa8b completed March 7, 2026, 7:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69b01d3d6a54819090068ef1807ca921 completed March 10, 2026, 1:31 p.m.
Created at: March 6, 2026, 9:54 p.m.