Triple
T16978162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarenput I |
E411867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Kingdom official |
C12919
|
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 official Context triple: [Sarenput I, instanceOf, Middle Kingdom official]
-
A.
ancient Egyptian official
chosen
An ancient Egyptian official was a government administrator or bureaucrat responsible for managing state affairs such as taxation, justice, temple estates, and regional governance under the authority of the pharaoh.
-
B.
Person of the Sixth Dynasty of Egypt
A Person of the Sixth Dynasty of Egypt is an individual who lived under the rule of the Sixth Dynasty pharaohs (c. 2345–2181 BCE), participating in the political, social, religious, or economic life of Old Kingdom Egypt during its final phase.
-
C.
Theban statesman
A Theban statesman is a political leader or public official from the ancient Greek city of Thebes who shaped its domestic policies, military strategies, and diplomatic relations within the Greek world.
-
D.
Middle Kingdom monument
A Middle Kingdom monument is a commemorative or religious structure built during Egypt’s Middle Kingdom (c. 2055–1650 BCE), reflecting the period’s political consolidation, artistic refinement, and evolving funerary and cult practices.
-
E.
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.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.