Triple
T9148311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangtown |
E219515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic town name |
C4613
|
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 town name Context triple: [Hangtown, instanceOf, historic town name]
-
A.
historic town
A historic town is a settlement characterized by preserved architecture, landmarks, and cultural features that reflect significant events, periods, or traditions from the past.
-
B.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
C.
historic township
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
D.
historic town common
A historic town common is a centrally located, publicly owned open space in a town that historically served as a communal gathering, grazing, and civic area and often remains a focal point for community events and heritage.
-
E.
historic mill town
A historic mill town is a community that developed around water- or steam-powered mills, where industrial buildings, worker housing, and civic structures reflect the town’s past as a center of manufacturing and economic activity.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:20 p.m.