Triple
T35183574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paucartambo |
E1015920
|
entity |
| Predicate | approximateDistanceInMilesFromCusco |
P14767
|
FINISHED |
| Object | approximately 62 miles |
—
|
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 62 miles | Statement: [Paucartambo, approximateDistanceInMilesFromCusco, approximately 62 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceInMilesFromCusco Context triple: [Paucartambo, approximateDistanceInMilesFromCusco, approximately 62 miles]
-
A.
distanceFromCusco
chosen
Indicates the measured spatial distance between a given location or entity and the city of Cusco.
-
B.
distanceFromArequipa
Indicates the spatial distance between a given location and the city of Arequipa.
-
C.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
-
D.
distanceFromLima
Indicates the measured distance between a given place or object and the city of Lima.
-
E.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:02 p.m.