Triple
T28969518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Bufadora |
E734231
|
entity |
| Predicate | approximateDistanceFromEnsenada |
P97899
|
FINISHED |
| Object | about 35 kilometers 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 35 kilometers south | Statement: [La Bufadora, approximateDistanceFromEnsenada, about 35 kilometers south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceFromEnsenada Context triple: [La Bufadora, approximateDistanceFromEnsenada, about 35 kilometers south]
-
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.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
D.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
-
E.
approximateDistanceToElPaso
Indicates that one entity has an estimated or rough distance measurement relative to the location of El Paso.
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 9:04 a.m.