Triple
T37000822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court House Square, Hamilton townsite |
E915343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic urban block |
C6702
|
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 block Context triple: [Court House Square, Hamilton townsite, instanceOf, historic urban block]
-
A.
historic block
A historic block is a contiguous group of buildings, streets, and public spaces recognized for their architectural, cultural, or historical significance and preserved to maintain their original character.
-
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 city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
-
D.
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.
-
E.
historic city square
chosen
A historic city square is a central public open space in a town or city, typically surrounded by significant buildings and monuments, that has served as a focal point for social, political, and commercial activities over time.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.