Triple
T16037110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puruchuco |
E388996
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Inca administrative center |
C1485
|
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: Inca administrative center Context triple: [Puruchuco, instanceOf, Inca administrative center]
-
A.
Incan citadel
chosen
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
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.
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.
-
E.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.