Triple
T14285924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado de Toluca National Park |
E354174
|
entity |
| Predicate | distanceFromToluca |
P113612
|
FINISHED |
| Object | approximately 20–30 kilometers southwest |
—
|
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 20–30 kilometers southwest | Statement: [Nevado de Toluca National Park, distanceFromToluca, approximately 20–30 kilometers southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromToluca Context triple: [Nevado de Toluca National Park, distanceFromToluca, approximately 20–30 kilometers southwest]
-
A.
distanceFromMexicoCity
Indicates the measured distance between an entity’s location and Mexico City.
-
B.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
C.
distanceToGuadalajara_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Guadalajara.
-
D.
distanceFromOaxacaCity
Indicates the spatial distance between a given place and Oaxaca City.
-
E.
distanceToMonterrey
Indicates the measured or specified distance between a given entity and the location of Monterrey.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.