Triple

T35737631
Position Surface form Disambiguated ID Type / Status
Subject Bryant Street (San Francisco) E1032934 entity
Predicate inStreetGridOf P12506 FINISHED
Object San Francisco street network 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: San Francisco street network | Statement: [Bryant Street (San Francisco), inStreetGridOf, San Francisco street network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inStreetGridOf
Context triple: [Bryant Street (San Francisco), inStreetGridOf, San Francisco street network]
  • A. streetGridExtendedFrom
    Indicates that one street grid layout continues or expands outward from another street grid as its extension.
  • B. hasStreetGridFeature
    Indicates that a location or area possesses a specific characteristic or element of a street grid layout, such as a particular pattern, structure, or feature of its road network.
  • C. streetGridRange
    Indicates the span or extent of a street segment within a defined grid or block range in a street network.
  • D. streetGridOrientation
    Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
  • E. hasStreetGridPattern chosen
    Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
  • 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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a34f8ee08190a040304635539a8f completed May 3, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69f7a06f125c8190843af194f042a465 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:05 p.m.