Triple
T10397383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senusret II |
E245054
|
entity |
| Predicate | praenomen |
P7966
|
FINISHED |
| Object | Khakheperre |
E1043199
|
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: Khakheperre | Statement: [Senusret II, praenomen, Khakheperre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khakheperre Context triple: [Senusret II, praenomen, Khakheperre]
-
A.
Khakheperre
chosen
Khakheperre was the throne name of the ancient Egyptian pharaoh Senusret II of the Twelfth Dynasty.
-
B.
Aakheperure
Aakheperure was the throne name of the Egyptian pharaoh Amenhotep II of the 18th Dynasty.
-
C.
Djedefhor
Djedefhor was an ancient Egyptian prince of the 4th Dynasty, known from wisdom literature and inscriptions as a royal son and court official during the Old Kingdom.
-
D.
Sobekkare
Sobekkare is the throne name (praenomen) of Sobekneferu, a queen who ruled as a pharaoh of ancient Egypt at the end of the Twelfth Dynasty.
-
E.
Sekhemkheperre
Sekhemkheperre is the throne name (prenomen) of the ancient Egyptian pharaoh Osorkon I of the 22nd Dynasty.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d0de448190b0bfd4d6c87d47fa |
completed | April 7, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75462fe9081908b939a1c6bdba6b9 |
completed | May 3, 2026, 1:57 p.m. |
Created at: April 6, 2026, 12:07 p.m.