Triple
T15186887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun-her-khepeshef |
E362898
|
entity |
| Predicate | hasNameElement |
P3097
|
FINISHED |
| Object | khepeshef |
E362898
|
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: khepeshef | Statement: [Amun-her-khepeshef, hasNameElement, khepeshef]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: khepeshef Context triple: [Amun-her-khepeshef, hasNameElement, khepeshef]
-
A.
Kheperkara
Kheperkara is the throne name of the ancient Egyptian pharaoh Senusret I of the Twelfth Dynasty.
-
B.
Djedkheperew
Djedkheperew was a relatively obscure pharaoh of Egypt’s 13th Dynasty, known primarily from limited archaeological and textual evidence dating to the early Second Intermediate Period.
-
C.
Amun-her-khepeshef
chosen
Amun-her-khepeshef was a crown prince of ancient Egypt’s 19th Dynasty and the eldest son and heir apparent of Pharaoh Ramesses II.
-
D.
Kha-sekhemui
Kha-sekhemui, better known as Khasekhemwy, was a pharaoh of Egypt’s Second Dynasty noted for reuniting Upper and Lower Egypt and for his distinctive monuments at Hierakonpolis and Abydos.
-
E.
Seshseshet
Seshseshet was an ancient Egyptian princess of the 6th Dynasty, known as a daughter of Pharaoh Teti.
- 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.