Triple
T13539391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro Blanco (Nepeña Valley) |
E323343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Early Horizon site |
C12166
|
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: Early Horizon site Context triple: [Cerro Blanco (Nepeña Valley), instanceOf, Early Horizon site]
-
A.
early medieval site
An early medieval site is an archaeological location dating roughly from the 5th to the 11th century CE that preserves material evidence of social, political, economic, and religious life during the early Middle Ages.
-
B.
Iron Age site
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
C.
pre-Columbian site
chosen
A pre-Columbian site is an archaeological location in the Americas that preserves evidence of human activity and cultures that existed before the arrival of Christopher Columbus in 1492.
-
D.
ancient village site
An ancient village site is an archaeological location preserving the remains of a past community’s dwellings, activity areas, and material culture, offering evidence of its social, economic, and environmental history.
-
E.
Predynastic Egyptian site
A Predynastic Egyptian site is an archaeological location in Egypt dating to the period before the unification of the Nile Valley, characterized by early developments in settlement, burial practices, and material culture that preceded the Pharaonic state.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.