Triple
T16442838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Amunherkhepshef |
E399346
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Amunherkhepshef |
—
|
NE NERFINISHED |
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: Amunherkhepshef | Statement: [Tomb of Amunherkhepshef, namedAfter, Amunherkhepshef]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amunherkhepshef Context triple: [Tomb of Amunherkhepshef, namedAfter, Amunherkhepshef]
-
A.
Amenherkhepshef
chosen
Amenherkhepshef was an ancient Egyptian prince of the 20th Dynasty, known primarily as a son of Pharaoh Ramesses VI.
-
B.
Menkheperre
Menkheperre is the throne name of the ancient Egyptian pharaoh Thutmose III, one of the most powerful rulers of the 18th Dynasty.
-
C.
Sekhemkheperre
Sekhemkheperre is the throne name (prenomen) of the ancient Egyptian pharaoh Osorkon I of the 22nd Dynasty.
-
D.
Menkheperure
Menkheperure is the throne name of Pharaoh Thutmose IV, an 18th Dynasty ruler of ancient Egypt.
-
E.
Merkheperre
Merkheperre was a relatively obscure pharaoh of ancient Egypt’s Second Intermediate Period, ruling during the later part of the 13th Dynasty.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd8d2988190acb5722a15623319 |
completed | April 18, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:10 a.m.