Triple
T16075675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ay |
E389973
|
entity |
| Predicate | praenomen |
P7966
|
FINISHED |
| Object | Kheperkheperure |
—
|
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: Kheperkheperure | Statement: [Ay, praenomen, Kheperkheperure]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kheperkheperure Context triple: [Ay, praenomen, Kheperkheperure]
-
A.
Kheperkheperure
chosen
Kheperkheperure is the throne name of the ancient Egyptian pharaoh Ay, who ruled briefly at the end of the 18th Dynasty following Tutankhamun.
-
B.
Menkheperure
Menkheperure is the throne name of Pharaoh Thutmose IV, an 18th Dynasty ruler of ancient Egypt.
-
C.
Menkheperre
Menkheperre is the throne name of the ancient Egyptian pharaoh Thutmose III, one of the most powerful rulers of the 18th Dynasty.
-
D.
Merkheperre
Merkheperre was a relatively obscure pharaoh of ancient Egypt’s Second Intermediate Period, ruling during the later part of the 13th Dynasty.
-
E.
Khakheperre
Khakheperre was the throne name of the ancient Egyptian pharaoh Senusret II of the Twelfth 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183c27aac81909c56d200c0c51a0c |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 4:57 a.m.