Triple
T12410144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca causeways |
E296493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Inca road system |
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: component of the Inca road system Context triple: [Inca causeways, instanceOf, component of the Inca road system]
-
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.
Inca engineering work
chosen
Inca engineering work encompasses the sophisticated design and construction of terraces, roads, bridges, and water systems that skillfully adapted to and harnessed the challenging Andean landscape.
-
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.
Colombian national highway
A Colombian national highway is a major road within Colombia’s national road network that connects key cities, regions, and borders to support transportation, commerce, and mobility across the country.
-
E.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.