Triple
T7954179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felipe Ángeles International Airport |
E184688
|
entity |
| Predicate | distanceFromMexicoCityCenter |
P45441
|
FINISHED |
| Object | about 45 km north |
—
|
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 45 km north | Statement: [Felipe Ángeles International Airport, distanceFromMexicoCityCenter, about 45 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMexicoCityCenter Context triple: [Felipe Ángeles International Airport, distanceFromMexicoCityCenter, about 45 km north]
-
A.
distanceFromMexicoCity
chosen
Indicates the measured distance between an entity’s location and Mexico City.
-
B.
locatedInDirectionFromMexicoCityCenter
Indicates the relative compass direction in which one place is situated from the center of Mexico City.
-
C.
distanceFromOaxacaCity
Indicates the spatial distance between a given place and Oaxaca City.
-
D.
distanceToGuadalajara_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Guadalajara.
-
E.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5f74308190aa63a22c3d5feacc |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.