Triple
T11678899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca terraces |
E277563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Inca engineering work |
C29695
|
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 engineering work Context triple: [Inca terraces, instanceOf, Inca engineering work]
-
A.
Inca road system
The Inca road system was an extensive, sophisticated network of paved and unpaved routes spanning thousands of kilometers across the Andes, designed to connect and administer the vast Inca Empire through efficient communication, trade, and military movement.
-
B.
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.
-
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.
Wari archaeological site
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.
- F. None of above. chosen
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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.