Triple
T28969628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Sauzal de Rodríguez |
E734234
|
entity |
| Predicate | distanceToEnsenada |
P97899
|
FINISHED |
| Object | a few kilometers north of Ensenada |
—
|
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: a few kilometers north of Ensenada | Statement: [El Sauzal de Rodríguez, distanceToEnsenada, a few kilometers north of Ensenada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToEnsenada Context triple: [El Sauzal de Rodríguez, distanceToEnsenada, a few kilometers north of Ensenada]
-
A.
approxDistanceFromEnsenada
chosen
Indicates that one entity is located at an approximate distance from the reference location Ensenada.
-
B.
distanceToSanDiego
Indicates the measured or estimated distance between a given entity’s location and the city of San Diego.
-
C.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
-
D.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
E.
distanceToSanJosé
Indicates the spatial distance between a given entity and the location of San José.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: April 28, 2026, 9:04 a.m.