Triple
T15186886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun-her-khepeshef |
E362898
|
entity |
| Predicate | hasNameElement |
P3097
|
FINISHED |
| Object | Heru (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: Heru (Horus) | Statement: [Amun-her-khepeshef, hasNameElement, Heru (Horus)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heru (Horus) Context triple: [Amun-her-khepeshef, hasNameElement, Heru (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.
Wepwawet
Wepwawet is an ancient Egyptian jackal-headed war and funerary god, often depicted as a path-opener who guided kings and the dead.
-
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.
Ra-Horakhty
Ra-Horakhty is an ancient Egyptian solar deity who combines aspects of the sun god Ra and the sky god Horus, often depicted as a falcon-headed man crowned with a solar disk.
-
E.
Sobek
Sobek is an ancient Egyptian crocodile-headed god associated with the Nile, military power, and protection.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067995fc8190b048f15086bd42f0 |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec895b59c81908a09f8393a35aa13 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:09 a.m.