Triple

T34698399
Position Surface form Disambiguated ID Type / Status
Subject historic street network of Goslar E891096 entity
Predicate instanceOf P0 FINISHED
Object historic urban street network C1381 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: historic urban street network
Context triple: [historic street network of Goslar, instanceOf, historic urban street network]
  • A. historic urban layout chosen
    A historic urban layout is the enduring spatial arrangement of streets, plots, public spaces, and building patterns that reflects the social, economic, and cultural organization of a city in a past period.
  • B. historic urban center
    A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
  • C. historic alley
    A historic alley is a narrow passageway between buildings that preserves architectural features, materials, and spatial character from a past era, reflecting the cultural and urban history of its surroundings.
  • D. urban street grid
    An urban street grid is a planned network of intersecting streets, typically arranged in a regular, rectangular pattern, that organizes city blocks, guides movement, and shapes land use within an urban area.
  • E. historic civic space
    A historic civic space is a publicly accessible area of enduring cultural, political, or social significance where communities have traditionally gathered for collective activities, events, and civic life.
  • F. None of above.

Provenance (1 batch)

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_69f349db7ab8819086808e833f472871 completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 2:05 a.m.