Triple

T34506536
Position Surface form Disambiguated ID Type / Status
Subject Hegewisch E885901 entity
Predicate hasStreetGridAlignment P5264 FINISHED
Object Chicago street grid 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: Chicago street grid | Statement: [Hegewisch, hasStreetGridAlignment, Chicago street grid]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStreetGridAlignment
Context triple: [Hegewisch, hasStreetGridAlignment, Chicago street grid]
  • A. hasStreetGridPattern
    Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
  • 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. hasStreetGridContext
    Indicates that one entity is situated within, influenced by, or characterized in relation to the street grid pattern or layout of another entity.
  • D. streetGridOrientation chosen
    Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
  • E. streetGridExtendedFrom
    Indicates that one street grid layout continues or expands outward from another street grid as its extension.
  • 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_69f349cc0220819081f154c6964f4dc2 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff9b1ad27081908f8a492396950795 completed May 9, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69ff9a6354c48190ae21070c1424cb7a completed May 9, 2026, 8:34 p.m.
Created at: May 1, 2026, 2:01 a.m.