Triple
T3565335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Street and Castro Street |
E75433
|
entity |
| Predicate | streetType_MarketStreet |
P50399
|
FINISHED |
| Object | major arterial street |
—
|
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: major arterial street | Statement: [Market Street and Castro Street, streetType_MarketStreet, major arterial street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetType_MarketStreet Context triple: [Market Street and Castro Street, streetType_MarketStreet, major arterial street]
-
A.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
-
C.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
D.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
E.
hasMainStreet
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a8f6288190928479f5bea32245 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:21 p.m.