Triple
T3007165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacaya |
E81930
|
entity |
| Predicate | distanceToGuatemalaCity |
P44618
|
FINISHED |
| Object | about 30 km south |
—
|
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: about 30 km south | Statement: [Pacaya, distanceToGuatemalaCity, about 30 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGuatemalaCity Context triple: [Pacaya, distanceToGuatemalaCity, about 30 km south]
-
A.
distanceToCancun
Indicates the measured or calculated spatial distance between a given entity and the location of Cancun.
-
B.
distanceFromOaxacaCity
Indicates the spatial distance between a given place and Oaxaca City.
-
C.
distanceToTulum
Indicates the measured or relative distance between a given entity or location and Tulum.
-
D.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
-
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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4a12508190a48ae1c86233d25e |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.