Triple
T7318733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-fifth Dynasty of Egypt |
E168482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kushite dynasty |
C19907
|
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: Kushite dynasty Context triple: [Twenty-fifth Dynasty of Egypt, instanceOf, Kushite dynasty]
-
A.
Ethiopian dynasty
An Ethiopian dynasty is a succession of rulers from the same lineage or family that governed Ethiopia over a historical period, often legitimized by claims of divine or ancestral authority.
-
B.
Kushite king
chosen
A Kushite king is a sovereign ruler of the ancient Nubian kingdom of Kush, often governing from cities like Napata or Meroë and at times ruling over Egypt as a pharaoh during the 25th Dynasty.
-
C.
Twenty-Sixth Dynasty of Egypt
The Twenty-Sixth Dynasty of Egypt, also known as the Saite Period (c. 664–525 BCE), was a late native Egyptian dynasty marked by political reunification, cultural revival, and increased interaction with Greek and Near Eastern powers before the Persian conquest.
-
D.
ruler of Meroë
A ruler of Meroë is the sovereign monarch—often titled king or kandake—who governed the ancient Kushite city of Meroë, overseeing its political, military, economic, and religious life.
-
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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
Created at: March 27, 2026, 3:02 p.m.