Triple

T19540394
Position Surface form Disambiguated ID Type / Status
Subject Ecuadorian Andes E488882 entity
Predicate contains P35 FINISHED
Object Riobamba 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: Riobamba | Statement: [Ecuadorian Andes, contains, Riobamba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riobamba
Context triple: [Ecuadorian Andes, contains, Riobamba]
  • A. Riobamba chosen
    Riobamba is a city in the central highlands of Ecuador, known as a gateway to the Andes and nearby Chimborazo volcano.
  • B. Tumebamba
    Tumebamba was a prominent Inca imperial city in the northern highlands, serving as a key administrative and ceremonial center in what is now southern Ecuador.
  • C. Huacaybamba
    Huacaybamba is a town in the Huánuco Region of central Peru that serves as the administrative and commercial center of the surrounding rural province.
  • D. Ouahigouya
    Ouahigouya is a major city in northern Burkina Faso known as an important commercial and administrative center of the region.
  • E. Pargua
    Pargua is a small coastal village in southern Chile that serves as a key ferry terminal and gateway to Chiloé Island across the Chacao Channel.
  • 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_69d8e8db5b6c8190984b61f91981f575 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63871d00881909ed7371ae5577957 completed April 20, 2026, 2:30 p.m.
Created at: April 10, 2026, 1:41 p.m.