Triple
T11678898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca terraces |
E277563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Columbian agricultural infrastructure |
C22633
|
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: pre-Columbian agricultural infrastructure Context triple: [Inca terraces, instanceOf, pre-Columbian agricultural infrastructure]
-
A.
pre-Columbian architecture
chosen
Pre-Columbian architecture encompasses the diverse and sophisticated building traditions of the Americas before European contact, including monumental pyramids, temples, palaces, and urban centers constructed by civilizations such as the Maya, Aztec, and Inca.
-
B.
Pre-Columbian culture
Pre-Columbian culture encompasses the diverse societies, traditions, technologies, and belief systems that existed throughout the Americas before the arrival of Christopher Columbus and subsequent European contact.
-
C.
pre-Columbian site
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.
pre-Columbian building
A pre-Columbian building is a structure constructed in the Americas before European contact, reflecting the architectural styles, materials, and cultural practices of indigenous civilizations such as the Maya, Aztec, and Inca.
-
E.
pre-Columbian cultural area
A pre-Columbian cultural area is a geographically defined region of the Americas characterized by shared cultural, social, and technological traits among Indigenous societies prior to European contact.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.