Triple

T2773945
Position Surface form Disambiguated ID Type / Status
Subject Manco Cápac E61523 entity
Predicate parent P120 FINISHED
Object Viracocha E61083 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: Viracocha | Statement: [Manco Cápac, parent, Viracocha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viracocha
Context triple: [Manco Cápac, parent, Viracocha]
  • A. Viracocha chosen
    Viracocha is the great creator god in Inca mythology, credited with forming the world, humanity, and other deities.
  • B. 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.
  • C. Sapa Inca
    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.
  • D. 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.
  • E. 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.
  • 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_69ab4b7cd13481909174bca9809ed259 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdd7e29e08190921fd4ac9d0679ec completed March 7, 2026, 8:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69b03121c93481909bee6711fab0ee0a completed March 10, 2026, 2:56 p.m.
Created at: March 6, 2026, 9:57 p.m.