Triple
T22096006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Vilcabamba |
E546034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Inca capital |
C11539
|
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: former Inca capital Context triple: [Old Vilcabamba, instanceOf, former Inca capital]
-
A.
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.
-
B.
pre-Columbian city
chosen
A pre-Columbian city is a large, organized urban settlement in the Americas that existed before European contact, characterized by complex social, political, economic, and religious structures.
-
C.
region of the Inca Empire
A region of the Inca Empire is a geographically defined administrative area governed by imperial officials to organize tribute, labor, and local affairs within the broader imperial structure.
-
D.
Recuay culture site
A Recuay culture site is an archaeological location associated with the Recuay civilization of the north-central highlands of Peru, characterized by its distinctive stone architecture, sculptural art, and funerary structures dating roughly from 200 BCE to 600 CE.
-
E.
Chimú civilization site
A Chimú civilization site is an archaeological location associated with the pre-Columbian Chimú culture, characterized by adobe architecture, intricate urban planning, and evidence of complex social, economic, and religious activities along Peru’s northern coast.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:30 p.m.