Triple
T24336120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quillacollo |
E613385
|
entity |
| Predicate | distanceToCochabamba |
P155756
|
FINISHED |
| Object | approximately 13 kilometers west |
—
|
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 13 kilometers west | Statement: [Quillacollo, distanceToCochabamba, approximately 13 kilometers west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCochabamba Context triple: [Quillacollo, distanceToCochabamba, approximately 13 kilometers west]
-
A.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
-
B.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
-
C.
distanceFromCafayateByRoad_km
Indicates the distance in kilometers from Cafayate to another location when traveling by road.
-
D.
distanceFromArequipa
Indicates the spatial distance between a given location and the city of Arequipa.
-
E.
distanceFromCusco
Indicates the measured spatial distance between a given location or entity and the city of Cusco.
- F. None of above. chosen
Provenance (4 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f5346881909ca93b7ceef543ed |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:56 a.m.