Triple
T32071043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savannah street grid |
E819011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic city plan |
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 city plan Context triple: [Savannah street grid, instanceOf, historic city plan]
-
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 district plan
A historic district plan is a comprehensive guiding document that outlines policies, design standards, and preservation strategies to protect and enhance the cultural, architectural, and historical character of a designated area.
-
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.
historic city-state
A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
-
E.
history of a city
A history of a city is a chronological account that traces the city’s origins, development, key events, and transformations over time, highlighting the social, political, economic, and cultural forces that shaped it.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:23 a.m.