Triple

T22096027
Position Surface form Disambiguated ID Type / Status
Subject Old Vilcabamba E546034 entity
Predicate alsoKnownAs P39 FINISHED
Object Vilcabamba the Old NE NERFINISHED

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: Vilcabamba the Old | Statement: [Old Vilcabamba, alsoKnownAs, Vilcabamba the Old]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vilcabamba the Old
Context triple: [Old Vilcabamba, alsoKnownAs, Vilcabamba the Old]
  • A. Vilcabamba
    Vilcabamba was the remote Andean stronghold that served as the last refuge of the Inca resistance against Spanish conquest.
  • B. Vilcabamba
    Vilcabamba is a small town in southern Ecuador’s Loja Province, known for its scenic Andean valley setting and reputation for residents’ longevity.
  • C. Suitucancha
    Suitucancha is a small Andean town and district located in the Yauli Province of Peru’s Junín Region.
  • D. 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.
  • E. Old Vilcabamba chosen
    Old Vilcabamba is the historical Inca settlement in Peru that served as the last stronghold of the Inca Empire during its resistance against Spanish conquest.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e36d03c8190a83a1ba802b7231b completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128e8f1f48190a5f1d9e96a6de688 completed April 28, 2026, 9:38 p.m.
Created at: April 16, 2026, 8:30 p.m.