Triple

T2858833
Position Surface form Disambiguated ID Type / Status
Subject Chinchaysuyu E63267 entity
Predicate ruledBy P3022 FINISHED
Object Sapa Inca E61193 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: Sapa Inca | Statement: [Chinchaysuyu, ruledBy, Sapa Inca]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sapa Inca
Context triple: [Chinchaysuyu, ruledBy, Sapa Inca]
  • A. Sapa Inca chosen
    The Sapa Inca was the supreme monarch and considered a divine son of the sun god Inti, holding absolute political and religious authority over the Inca civilization.
  • B. Huayna Capac
    Huayna Capac was a late 15th–early 16th century Sapa Inca whose reign marked the territorial peak of the Inca Empire shortly before the Spanish conquest.
  • C. Manco Cápac
    Manco Cápac is the legendary founder and first Sapa Inca of the Inca civilization, traditionally credited with establishing its capital at Cusco.
  • D. Pachacámac
    Pachacámac is a district in the Lima Province of Peru, known for its important pre-Columbian archaeological site and temples dedicated to the deity Pachacámac.
  • E. Topa Inca Yupanqui
    Topa Inca Yupanqui was a powerful Sapa Inca of the 15th century who greatly expanded the Inca Empire’s territory through extensive military campaigns and consolidation of conquered regions.
  • 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_69b324d0152881909526cf9079560dc6 completed March 12, 2026, 8:40 p.m.
Created at: March 6, 2026, 10:02 p.m.