Triple
T11330909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colta |
E268339
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Riobamba |
E55989
|
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: Riobamba | Statement: [Colta, near, Riobamba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riobamba Context triple: [Colta, near, 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.
Ouahigouya
Ouahigouya is a major city in northern Burkina Faso known as an important commercial and administrative center of the region.
-
D.
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.
-
E.
Urubamba
Urubamba is a town in Peru’s Sacred Valley of the Incas, known as a gateway to Machu Picchu and surrounding Andean archaeological sites.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5564218bc8190bbaf9aceb69fdc26 |
completed | April 19, 2026, 10:25 p.m. |
Created at: April 8, 2026, 9:32 p.m.