Triple
T25389143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saite kingdom |
E631610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian kingdom |
C4291
|
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: ancient Egyptian kingdom Context triple: [Saite kingdom, instanceOf, ancient Egyptian kingdom]
-
A.
Ancient Egyptian dynasty
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.
period of ancient Egypt
A period of ancient Egypt is a distinct span of time in Egyptian history characterized by specific political structures, cultural developments, dynastic rule, and major events that differentiate it from other eras.
-
C.
ancient kingdom
chosen
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
D.
ancient Near Eastern dynasty
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
E.
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.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:47 p.m.