Triple
T31829210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Ysidro |
E812480
|
entity |
| Predicate | positionWithinSanDiego |
P197520
|
FINISHED |
| Object | southernmost community |
—
|
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: southernmost community | Statement: [San Ysidro, positionWithinSanDiego, southernmost community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinSanDiego Context triple: [San Ysidro, positionWithinSanDiego, southernmost community]
-
A.
distanceToSanDiego
Indicates the measured or estimated distance between a given entity’s location and the city of San Diego.
-
B.
distanceFromSanJosé
Indicates the measured spatial distance between a given entity and the location of San José.
-
C.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
-
D.
directionFromSanDiegoDowntown
Indicates the compass direction or bearing from downtown San Diego to another location.
-
E.
distanceToSanJosé
Indicates the spatial distance between a given entity and the location of San José.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69fe991abc6c81908edbb98d61c9ca73 |
completed | May 9, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:47 p.m.