Triple

T3083275
Position Surface form Disambiguated ID Type / Status
Subject Cuntisuyu E64307 entity
Predicate instanceOf P0 FINISHED
Object Inca territorial division C11794 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 territorial division
Context triple: [Cuntisuyu, instanceOf, Inca territorial division]
  • A. 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.
  • B. 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.
  • C. Andean chronological period
    An Andean chronological period is a defined span of time used by archaeologists and historians to organize and interpret the cultural, political, and technological development of societies in the Andean region of South America.
  • D. battle of the Spanish conquest of Peru
    A battle of the Spanish conquest of Peru is a specific military engagement between Spanish conquistadors and Indigenous forces that occurred during the 16th-century campaign to subjugate and colonize the Inca Empire.
  • E. Inca quarter chosen
    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.

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_69ad857bb4c88190a4cf27893fcabed8 completed March 8, 2026, 2:19 p.m.
Created at: March 8, 2026, 3:03 p.m.