Triple
T25667963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick Historic District |
E643577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railroad town historic district |
C9390
|
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: railroad town historic district Context triple: [Brunswick Historic District, instanceOf, railroad town historic district]
-
A.
historic railroad town
A historic railroad town is a community whose growth, economy, and cultural identity were fundamentally shaped by its role as a hub or stop along early railway lines.
-
B.
historic railroad right-of-way
A historic railroad right-of-way is a corridor of land formerly used for railroad tracks and associated infrastructure that retains cultural, transportation, or engineering significance despite no longer serving active rail operations.
-
C.
railway town
chosen
A railway town is a settlement whose origin, growth, and economic life are primarily shaped by the construction, operation, and services of a nearby railway line or station.
-
D.
reconstructed historic district
A reconstructed historic district is an area where buildings, streetscapes, and public spaces have been rebuilt or extensively restored to replicate their historical appearance and character, often based on archival research and archaeological evidence.
-
E.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:08 p.m.