Triple
T33927056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11th Street (San Francisco) |
E869780
|
entity |
| Predicate | hasNeighborhoodOnWest |
P200623
|
FINISHED |
| Object | South of Market, San Francisco |
—
|
NE NERFINISHED |
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 of Market, San Francisco | Statement: [11th Street (San Francisco), hasNeighborhoodOnWest, South of Market, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborhoodOnWest Context triple: [11th Street (San Francisco), hasNeighborhoodOnWest, South of Market, San Francisco]
-
A.
hasTerminusWest
Indicates that something has its western endpoint, terminus, or final stop at the referenced entity.
-
B.
hasNeighboringStateToWest
Indicates that one state is geographically located directly to the west of another state, sharing a common border.
-
C.
hasNorthNeighbor
Indicates that one entity is located directly to the north of another entity.
-
D.
adjacentRouteWest
Indicates that one route is directly adjacent to another on its western side.
-
E.
hasNeighborhoodAlong
Indicates that one entity has a neighboring area or region that extends along the boundary or length of another entity.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69ff9bec9d748190869caebf6bf0c78f |
completed | May 9, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:49 a.m.