Triple

T12274702
Position Surface form Disambiguated ID Type / Status
Subject Inca messengers E292559 entity
Predicate instanceOf P0 FINISHED
Object Inca road system personnel C31209 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 road system personnel
Context triple: [Inca messengers, instanceOf, Inca road system personnel]
  • 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
    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. Inca imperial policy
    Inca imperial policy was a centralized system of governance that combined military conquest, forced resettlement, standardized administration, and state-managed economy and religion to integrate diverse Andean peoples under the authority of the Sapa Inca.
  • D. 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.
  • E. Inca quarter
    An Inca quarter is an administrative and territorial division of the Inca Empire, representing one of the four major regions (suyus) that radiated from the capital, Cusco.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
Created at: April 8, 2026, 9:52 p.m.