Triple

T2773944
Position Surface form Disambiguated ID Type / Status
Subject Manco Cápac E61523 entity
Predicate parent P120 FINISHED
Object Inti E60004 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: Inti | Statement: [Manco Cápac, parent, Inti]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inti
Context triple: [Manco Cápac, parent, Inti]
  • A. Inti chosen
    Inti is the Incan sun god, revered as a principal deity associated with royal power, agriculture, and the cosmic order.
  • B. Surya
    Surya is the Hindu sun god revered as a major solar deity associated with light, power, and vitality.
  • C. Varuna
    Varuna is an ancient Vedic god primarily associated with cosmic order, moral law, and the waters, often regarded as a sovereign guardian of ṛta (universal order).
  • D. Varuna
    Varuna is a large, rapidly rotating trans-Neptunian object in the Kuiper Belt, notable for its elongated shape and classification as a likely dwarf-planet candidate.
  • E. Shesha
    Shesha is the cosmic serpent in Hindu mythology who serves as the divine couch of Lord Vishnu and symbolizes eternity and the foundation of the universe.
  • 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_69afc64c83748190921589bec20dec58 completed March 10, 2026, 7:20 a.m.
Created at: March 6, 2026, 9:57 p.m.