Triple
T12034054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McClellan–Palomar Airport |
E286487
|
entity |
| Predicate | distanceToDowntownCarlsbad |
P68801
|
FINISHED |
| Object | approximately 3 miles southeast |
—
|
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 3 miles southeast | Statement: [McClellan–Palomar Airport, distanceToDowntownCarlsbad, approximately 3 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDowntownCarlsbad Context triple: [McClellan–Palomar Airport, distanceToDowntownCarlsbad, approximately 3 miles southeast]
-
A.
distanceFromCarlsbad
chosen
Indicates the measured spatial distance between a given entity or location and Carlsbad.
-
B.
distanceToSanDiego
Indicates the measured or estimated distance between a given entity’s location and the city of San Diego.
-
C.
distanceToCorpusChristi
Indicates the spatial distance between a given entity’s location and the location of Corpus Christi.
-
D.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
-
E.
approxDistanceFromEnsenada
Indicates that one entity is located at an approximate distance from the reference location Ensenada.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.