Triple
T26743958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caburgua |
E674341
|
entity |
| Predicate | distanceFromPucón |
P180394
|
FINISHED |
| Object | approximately 23 kilometers |
—
|
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 23 kilometers | Statement: [Caburgua, distanceFromPucón, approximately 23 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPucón Context triple: [Caburgua, distanceFromPucón, approximately 23 kilometers]
-
A.
approxDistanceFromPucón
chosen
Indicates an approximate spatial distance measured from the location of Pucón to another place or entity.
-
B.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
-
C.
distanceToTalca_km
Indicates the physical distance, measured in kilometers, between a given entity and the city of Talca.
-
D.
distanceFromPurmamarca
Indicates the measured distance separating a given entity or location from Purmamarca.
-
E.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 27, 2026, 3:50 a.m.