Triple
T11325160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramos Arizpe |
E268192
|
entity |
| Predicate | distanceToSaltillo_km |
P98509
|
FINISHED |
| Object | approximately 15 |
—
|
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 15 | Statement: [Ramos Arizpe, distanceToSaltillo_km, approximately 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSaltillo_km Context triple: [Ramos Arizpe, distanceToSaltillo_km, approximately 15]
-
A.
distanceToGuadalajara_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Guadalajara.
-
B.
distanceFromMexicoCity
Indicates the measured distance between an entity’s location and Mexico City.
-
C.
distanceFromOaxacaCity
Indicates the spatial distance between a given place and Oaxaca City.
-
D.
distanceToMonterrey
Indicates the measured or specified distance between a given entity and the location of Monterrey.
-
E.
distanceToTepic
Indicates the spatial distance between an entity and the location Tepic.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.