Triple

T5369755
Position Surface form Disambiguated ID Type / Status
Subject San Miguel Topilejo E108816 entity
Predicate locatedNear P294 FINISHED
Object Ajusco E105106 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: Ajusco | Statement: [San Miguel Topilejo, locatedNear, Ajusco]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ajusco
Context triple: [San Miguel Topilejo, locatedNear, Ajusco]
  • A. Ajusco chosen
    Ajusco is a prominent volcanic mountain and national park in southern Mexico City, known for its high elevation, forests, and popular outdoor recreation areas.
  • B. Tezonco
    Tezonco is a metro station in Mexico City that serves the southeastern area of the city on the capital’s rapid transit network.
  • C. Xelajú
    Xelajú is the traditional Kʼicheʼ Maya name and commonly used nickname for the Guatemalan city of Quetzaltenango, a major cultural and economic center in the country’s western highlands.
  • D. Mixiuhca
    Mixiuhca is a Mexico City Metro station on Line 9 serving the eastern part of the city.
  • E. Ocoyoacac
    Ocoyoacac is a municipality in the State of Mexico located on the western edge of the Valley of Mexico, known for its forests, mountainous terrain, and proximity to Mexico City.
  • 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_69bd440c77948190aad2a5f39b7b80f5 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd86873e0c8190bf5ecede2cc2bd8b completed March 20, 2026, 5:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf292c4d1c819088f7b977ac212688 completed March 21, 2026, 11:26 p.m.
Created at: March 20, 2026, 2:02 p.m.