Triple
T26011303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacho, Cundinamarca, Colombia |
E646907
|
entity |
| Predicate | distanceToBogotá_km |
P29005
|
FINISHED |
| Object | approximately 88 |
—
|
LITERAL 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: approximately 88 | Statement: [Pacho, Cundinamarca, Colombia, distanceToBogotá_km, approximately 88]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBogotá_km Context triple: [Pacho, Cundinamarca, Colombia, distanceToBogotá_km, approximately 88]
-
A.
distanceFromBogotá
chosen
Indicates the spatial distance separating a given entity or location from the city of Bogotá.
-
B.
distanceFromMedellín
Indicates the measured spatial distance between an entity and the city of Medellín.
-
C.
distanceToSantaMarta
Indicates the measured spatial distance between a given entity’s location and the location of Santa Marta.
-
D.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
-
E.
directionFromBogotá
Indicates the cardinal or relative compass direction in which one place or object lies when measured from Bogotá.
- F. None of above.
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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 22, 2026, 9:01 a.m.