Triple
T10199165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenemhat I |
E238838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Kingdom ruler |
C27238
|
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: Middle Kingdom ruler Context triple: [Amenemhat I, instanceOf, Middle Kingdom ruler]
-
A.
Second Dynasty ruler
A Second Dynasty ruler is a monarch who governed ancient Egypt during its Second Dynasty (c. 2890–2686 BCE), overseeing early state consolidation, religious development, and royal institution building.
-
B.
Twelfth Dynasty pharaoh
chosen
A Twelfth Dynasty pharaoh is a ruler of ancient Egypt’s Middle Kingdom (c. 1991–1802 BCE) who centralized power, promoted administrative reforms, and oversaw significant cultural and architectural achievements.
-
C.
Third Dynasty pharaoh
A Third Dynasty pharaoh is an ancient Egyptian king who ruled during the early Old Kingdom (c. 2686–2613 BCE), overseeing the consolidation of state power and major innovations in stone architecture, including the earliest pyramids.
-
D.
king of Upper Egypt
A king of Upper Egypt is the sovereign ruler who governed the southern region of ancient Egypt, centered around cities like Thebes, often before and during its unification with Lower Egypt.
-
E.
ruler of the Twenty-second Dynasty of Egypt
A ruler of the Twenty-second Dynasty of Egypt is a pharaoh who governed during a Libyan-origin dynasty (c. 943–716 BCE), overseeing political, military, and religious affairs in a period marked by regional fragmentation and power-sharing with local elites.
- F. None of above.
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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:14 p.m.