Triple
T38088136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Additions to the pyramid complex of Neferirkare at Abusir |
E951030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of funerary complex |
C31069
|
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: component of funerary complex Context triple: [Additions to the pyramid complex of Neferirkare at Abusir, instanceOf, component of funerary complex]
-
A.
component of palace complex
A component of a palace complex is an individual architectural or functional unit—such as a hall, courtyard, gate, garden, or residential wing—that contributes to the overall structure, use, and symbolism of the palace ensemble.
-
B.
Funerary structure
chosen
A funerary structure is a built form or monument specifically designed to house, mark, or commemorate the dead and associated burial practices.
-
C.
section of mausoleum
A section of mausoleum is a distinct, often enclosed subdivision within a larger mausoleum structure, designed to house and organize multiple burial chambers or memorial niches.
-
D.
mastaba tomb complex
A mastaba tomb complex is an ancient Egyptian flat-roofed, rectangular funerary structure with sloping sides, typically built of mudbrick or stone, that served as a monumental above-ground marker and chapel for an underground burial chamber.
-
E.
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.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.