Triple
T20860154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huari archaeological site |
E513593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wari civilization site |
C26557
|
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: Wari civilization site Context triple: [Huari archaeological site, instanceOf, Wari civilization site]
-
A.
Wari site
A Wari site is an archaeological location associated with the Wari (Huari) civilization of the central Andes, characterized by planned urban centers, administrative compounds, and distinctive architectural and material culture remains dating roughly from 600–1000 CE.
-
B.
Wari archaeological site
chosen
The Wari archaeological site is the remains of an ancient Andean urban and ceremonial center associated with the Wari civilization, featuring complex architecture, administrative compounds, and evidence of early imperial organization in pre-Inca Peru.
-
C.
Nazca culture site
A Nazca culture site is an archaeological location associated with the ancient Nazca civilization of southern Peru, characterized by features such as geoglyphs, ceremonial centers, settlements, and burial grounds that reflect their social, religious, and artistic practices.
-
D.
Moche pyramid
A Moche pyramid is a monumental, terraced adobe structure built by the Moche civilization of ancient Peru, serving as a ceremonial, administrative, and sometimes funerary center.
-
E.
Incan citadel
An Incan citadel is a fortified highland complex of stone-built structures, terraces, and ceremonial spaces that served as a political, religious, and military center of the Inca civilization.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.