Triple

T2858821
Position Surface form Disambiguated ID Type / Status
Subject Chinchaysuyu E63267 entity
Predicate borderedBy P224 FINISHED
Object Collasuyu E64167 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Collasuyu | Statement: [Chinchaysuyu, borderedBy, Collasuyu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Collasuyu
Context triple: [Chinchaysuyu, borderedBy, Collasuyu]
  • A. Collasuyu chosen
    Collasuyu was the southeastern quarter of the Inca Empire, encompassing the highland and lowland regions around Lake Titicaca and extending into parts of present-day Bolivia, Chile, and Argentina.
  • B. Cuntisuyu
    Cuntisuyu was one of the four main administrative and territorial divisions of the Inca Empire, located to the southwest of Cusco.
  • C. Chinchaysuyu
    Chinchaysuyu was the northwestern quarter of the Inca Empire, encompassing coastal and highland regions that are now parts of Peru, Ecuador, and Colombia.
  • D. Vilcabamba
    Vilcabamba was the remote Andean stronghold that served as the last refuge of the Inca resistance against Spanish conquest.
  • E. Antisuyu
    Antisuyu was the eastern quarter of the Inca Empire, encompassing the Andean slopes and Amazonian frontier regions inhabited by various indigenous groups.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69ab4c41e8c08190a9e8f5249cc12610 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf89d3b4819086936f26d8683a2a completed March 7, 2026, 8:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69b03147229c81909e2f47f1ec40633d completed March 10, 2026, 2:57 p.m.
Created at: March 6, 2026, 10:02 p.m.