Triple
T8167416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamla Uppsala burial mounds |
E190726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | burial mound complex |
C4932
|
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: burial mound complex Context triple: [Gamla Uppsala burial mounds, instanceOf, burial mound complex]
-
A.
prehistoric underground burial complex
A prehistoric underground burial complex is a network of subterranean chambers and passages constructed by ancient societies to inter the dead, often accompanied by ritual artifacts and symbolic architecture.
-
B.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
C.
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.
-
D.
ancient building complex
chosen
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
E.
pyramid-shaped monument
A pyramid-shaped monument is a large, often stone-built, commemorative structure with a polygonal base and triangular sides that converge to a single apex, typically serving religious, funerary, or memorial purposes.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:39 p.m.