Triple
T27169465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkeperre Rudamun |
E682865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Twenty-third Dynasty pharaoh |
C52577
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Twenty-third Dynasty pharaoh Context triple: [Menkeperre Rudamun, instanceOf, Twenty-third Dynasty pharaoh]
-
A.
24th Dynasty pharaoh
A 24th Dynasty pharaoh is a ruler of ancient Egypt during the brief, Late Period dynasty (c. 732–720 BCE) centered in Sais, known for competing with the 25th (Kushite) Dynasty for control of the Nile Valley.
-
B.
29th Dynasty pharaoh
A 29th Dynasty pharaoh is a ruler of ancient Egypt during the Twenty-ninth Dynasty (c. 399–380 BCE), a short-lived native Egyptian dynasty marked by political instability and efforts to resist Persian domination.
-
C.
Twentieth Dynasty pharaoh
A Twentieth Dynasty pharaoh is a ruler of ancient Egypt’s final dynasty of the New Kingdom period (c. 1189–1077 BCE), overseeing a time of political decline, economic strain, and increasing external threats.
-
D.
Seventeenth Dynasty pharaoh
A Seventeenth Dynasty pharaoh is a ruler of ancient Egypt during the late Second Intermediate Period, primarily based in Thebes, who worked to resist Hyksos control and set the stage for the New Kingdom’s reunification.
-
E.
26th Dynasty ruler
A 26th Dynasty ruler is a pharaoh of Egypt’s Saite Period (c. 664–525 BCE) who governed from Sais, overseeing a cultural renaissance, administrative reforms, and renewed foreign engagements before the Persian conquest.
- F. None of above. chosen
Provenance (1 batch)
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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:22 a.m.