Triple
T13706621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ihy |
E328656
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Horus of Edfu |
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 of Edfu | Statement: [Ihy, father, Horus of Edfu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horus of Edfu Context triple: [Ihy, father, Horus of Edfu]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Pr-Medjed
Pr-Medjed is the ancient Egyptian name for the city later known as Oxyrhynchus, a prominent urban center in Middle Egypt famed for its rich trove of papyrus texts.
-
E.
Amun-her-khepeshef
Amun-her-khepeshef was a crown prince of ancient Egypt’s 19th Dynasty and the eldest son and heir apparent of Pharaoh Ramesses II.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad18d48c8190a26be865c31975d6 |
completed | April 13, 2026, 8:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b06554748190bf76e3383413a3c4 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.