Triple
T7823159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osorkon I |
E181180
|
entity |
| Predicate | throneName |
P25582
|
FINISHED |
| Object | Sekhemkheperre |
E695176
|
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: Sekhemkheperre | Statement: [Osorkon I, throneName, Sekhemkheperre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sekhemkheperre Context triple: [Osorkon I, throneName, Sekhemkheperre]
-
A.
Sekhemkheperre
chosen
Sekhemkheperre is the throne name (prenomen) of the ancient Egyptian pharaoh Osorkon I of the 22nd Dynasty.
-
B.
Sekhemkare
Sekhemkare was an ancient Egyptian prince of the 4th Dynasty, known as a son of Pharaoh Khafre and holder of high administrative and priestly offices.
-
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.
Nebkheperure
Nebkheperure is the throne name of the ancient Egyptian pharaoh Tutankhamun, used as part of his royal titulary during the 18th Dynasty.
-
E.
Bakenranef
Bakenranef was a short-lived pharaoh of Egypt’s 24th Dynasty, ruling from Sais in the western Delta during the politically fragmented Third Intermediate Period.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa095d7081908b3e492ce58b5d5f |
completed | March 30, 2026, 10:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5a66c1c0819087ce9890f28bb022 |
completed | March 31, 2026, 5:23 a.m. |
Created at: March 30, 2026, 4:42 p.m.