Triple
T3657304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose III |
E77562
|
entity |
| Predicate | praenomen |
P7966
|
FINISHED |
| Object | Menkheperre |
E377279
|
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: Menkheperre | Statement: [Thutmose III, praenomen, Menkheperre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Menkheperre Context triple: [Thutmose III, praenomen, Menkheperre]
-
A.
Menkheperre
chosen
Menkheperre is the throne name of the ancient Egyptian pharaoh Thutmose III, one of the most powerful rulers of the 18th Dynasty.
-
B.
Usermaatre Setepenre
Usermaatre Setepenre is the throne name of Ramesses II, one of ancient Egypt’s most powerful and long-reigning pharaohs of the New Kingdom.
-
C.
Men-nefer
Men-nefer is the ancient Egyptian name for the city later known as Memphis, a major political and religious center near modern Cairo.
-
D.
Menkheperure Thutmose
Menkheperure Thutmose was the birth name of Thutmose IV, a pharaoh of Egypt’s 18th Dynasty known for restoring the Great Sphinx and consolidating Egyptian power.
-
E.
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.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d36c1c8190920397a75de4c47d |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4c393f0608190a9af2cdc87bf83d9 |
completed | March 14, 2026, 2:10 a.m. |
Created at: March 8, 2026, 3:24 p.m.