Triple
T6687495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal tombs at Abydos |
E152135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian royal necropolis |
C6709
|
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 royal necropolis Context triple: [Royal tombs at Abydos, instanceOf, ancient Egyptian royal necropolis]
-
A.
New Kingdom burial complex
A New Kingdom burial complex is an architecturally elaborate mortuary installation—often including tombs, chapels, shafts, and associated cult spaces—designed to house and ritually sustain the dead within the religious and political landscape of New Kingdom Egypt.
-
B.
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.
-
C.
ancient Nubian site
An ancient Nubian site is an archaeological location in the Nile Valley region of Nubia that preserves the material remains, architecture, and cultural landscapes of the historic Nubian civilizations.
-
D.
ancient Egyptian city
chosen
An ancient Egyptian city is an urban settlement along the Nile characterized by monumental temples and tombs, administrative and residential districts, and a society organized around pharaonic rule, religion, and agriculture.
-
E.
Theban royal
A Theban royal is a member of the ruling dynasty of ancient Thebes, holding political, religious, and military authority within the city-state and its territories.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:04 p.m.