Triple
T31829209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Ysidro |
E812480
|
entity |
| Predicate | directionFromSanDiegoDowntown |
P192847
|
FINISHED |
| Object | 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: south | Statement: [San Ysidro, directionFromSanDiegoDowntown, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromSanDiegoDowntown Context triple: [San Ysidro, directionFromSanDiegoDowntown, south]
-
A.
directionFromSanFrancisco
Indicates the compass direction in which one location lies relative to San Francisco.
-
B.
directionRelativeToEmeraldCity
Indicates the compass direction or positional bearing of one place or object relative to the location of Emerald City.
-
C.
directionFromPhoenix
Indicates the cardinal or relative compass direction of an entity as measured from Phoenix.
-
D.
directionFromSantiago
Indicates the cardinal or relative compass direction of an entity as measured from the location of Santiago.
-
E.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
- 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_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: April 30, 2026, 11:47 p.m.