Triple
T32238811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winsted Industrial District |
E823548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic place in Connecticut |
C61418
|
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 place in Connecticut Context triple: [Winsted Industrial District, instanceOf, historic place in Connecticut]
-
A.
historic place in Massachusetts
A historic place in Massachusetts is a location, structure, or district within the state that holds recognized significance for its association with important events, people, architecture, or cultural heritage, often preserved and documented for its contribution to local or national history.
-
B.
town in Connecticut
A town in Connecticut is a municipal subdivision of the state with its own local government, defined geographic boundaries, and responsibility for providing community services to its residents.
-
C.
museum in Connecticut
A museum in Connecticut is a cultural institution within the state that collects, preserves, and exhibits art, artifacts, or historical materials for public education and enrichment.
-
D.
historic place in New York
A historic place in New York is a location within the state that holds recognized cultural, architectural, or historical significance, often preserved or commemorated for its role in the region’s past.
-
E.
Connecticut state park
A Connecticut state park is a publicly owned natural or recreational area within the state of Connecticut that is preserved, managed, and maintained by the state government for conservation, outdoor activities, and public enjoyment.
- F. None of above. chosen
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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.