Triple
T26095646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubian Dynasty |
E658257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Egyptian ruling dynasty |
C6302
|
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: Egyptian ruling dynasty Context triple: [Nubian Dynasty, instanceOf, Egyptian ruling dynasty]
-
A.
Ancient Egyptian dynasty
chosen
An Ancient Egyptian dynasty is a succession of rulers from the same family or lineage who governed Egypt during a distinct historical period, often characterized by shared political, cultural, and religious developments.
-
B.
Egyptian political dynasty
An Egyptian political dynasty is a succession of rulers from the same family or lineage that holds centralized authority over Egypt’s governance, religion, and society across multiple generations.
-
C.
25th Dynasty of Egypt ruler
A 25th Dynasty of Egypt ruler is a Kushite pharaoh who governed Egypt during the Nubian-led Twenty-fifth Dynasty (c. 744–656 BCE), known for reunifying the Nile Valley and promoting a revival of traditional Egyptian culture and religion.
-
D.
18th Dynasty pharaoh
An 18th Dynasty pharaoh is a monarch of ancient Egypt’s New Kingdom (c. 1550–1292 BCE) who wielded supreme political, military, and religious authority while overseeing a period of territorial expansion, artistic flourishing, and administrative centralization.
-
E.
Egyptian royal
An Egyptian royal is a member of the ruling family in ancient Egypt, typically a pharaoh or close relative, who holds political, religious, and ceremonial authority within the kingdom’s hierarchical society.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:50 p.m.