Triple
T29272036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersyankh III |
E742144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th Dynasty individual |
C20005
|
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: 4th Dynasty individual Context triple: [Mersyankh III, instanceOf, 4th Dynasty individual]
-
A.
4th Dynasty person
chosen
A 4th Dynasty person is an individual who lived in ancient Egypt during the 4th Dynasty (c. 2613–2494 BCE), typically associated with the Old Kingdom’s pyramid-building era and the royal court or society surrounding pharaohs like Khufu and Khafre.
-
B.
Fourth Dynasty pharaoh
A Fourth Dynasty pharaoh is an ancient Egyptian king who ruled during the Old Kingdom’s Fourth Dynasty (c. 2613–2494 BCE), overseeing centralized state power and monumental pyramid construction at Giza.
-
C.
Fifth Dynasty pharaoh
A Fifth Dynasty pharaoh was a ruler of ancient Egypt’s Old Kingdom (c. 25th–24th century BCE) who governed from Memphis, oversaw major pyramid and sun temple constructions, and reinforced the state cult of the sun god Ra.
-
D.
Fifth Dynasty person
A Fifth Dynasty person is an individual who lived in or is associated with the Fifth Dynasty of ancient Egypt (c. 2494–2345 BCE), typically connected to its royal court, administration, religion, or society.
-
E.
Sixth Dynasty pharaoh
A Sixth Dynasty pharaoh was a ruler of ancient Egypt during the late Old Kingdom (c. 2345–2181 BCE), overseeing centralized royal authority, monumental building projects, and complex administrative systems amid growing internal challenges.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:48 p.m.