Triple

T19322317
Position Surface form Disambiguated ID Type / Status
Subject Battle of Ayohuma E483255 entity
Predicate historicalRegion P915 FINISHED
Object Alto Perú 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: Alto Perú | Statement: [Battle of Ayohuma, historicalRegion, Alto Perú]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alto Perú
Context triple: [Battle of Ayohuma, historicalRegion, Alto Perú]
  • A. Alto Perú chosen
    Alto Perú was the colonial-era region in the central Andes that roughly corresponds to modern-day Bolivia and was a key mining and administrative center of the Spanish Empire in South America.
  • B. Guarayu
    Guarayu is an indigenous language of the Tupi–Guaraní family spoken primarily by the Guarayu people in eastern Bolivia.
  • C. Lumbaquí
    Lumbaquí is a small town in northeastern Ecuador that serves as a local hub within the Amazonian Sucumbíos Province.
  • D. Andahuaylas
    Andahuaylas is a city in the southern Peruvian Andes known as a commercial and cultural center for the surrounding rural highland communities.
  • E. Cuyoño
    Cuyoño is an Austronesian language spoken primarily in the Cuyo Islands and parts of Palawan in the Philippines.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e60d8948948190b76a384041333509 completed April 20, 2026, 11:27 a.m.
Created at: April 10, 2026, 1:32 p.m.