Triple
T35074465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American streetcar suburbs |
E1011972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical urban form |
C63090
|
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: historical urban form Context triple: [American streetcar suburbs, instanceOf, historical urban form]
-
A.
historic urban layout
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.
medieval urban system
A medieval urban system is the interconnected network of towns and cities, their institutions, economic activities, social hierarchies, and spatial arrangements that structured urban life and regional interactions in the Middle Ages.
-
C.
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.
-
D.
urban development pattern
chosen
An urban development pattern is the characteristic spatial arrangement and organization of buildings, infrastructure, and land uses within a city or metropolitan area, shaped by social, economic, environmental, and policy forces over time.
-
E.
Renaissance urban ensemble
A Renaissance urban ensemble is a cohesive grouping of buildings, streets, and public spaces that collectively embody the architectural, artistic, and spatial principles of the Renaissance period within a city.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.