Triple
T6812327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield, Connecticut Colony |
E156664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place on the Connecticut River |
C9011
|
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: populated place on the Connecticut River Context triple: [Enfield, Connecticut Colony, instanceOf, populated place on the Connecticut River]
-
A.
town in Connecticut
chosen
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.
-
B.
town in Massachusetts
A town in Massachusetts is a municipal entity with its own local government, typically governed by an open or representative town meeting and a board of selectmen, providing services and regulations for residents within its defined geographic boundaries.
-
C.
town in Maine
A town in Maine is a local governmental unit within the state of Maine that encompasses a defined geographic area, provides municipal services, and is governed by elected officials, often through a town meeting system.
-
D.
populated place on Lake Erie
A populated place on Lake Erie is a city, town, or settlement located along the shores or within the immediate coastal region of Lake Erie, whose geography, economy, and culture are significantly influenced by the lake.
-
E.
county of Connecticut
A county of Connecticut is an administrative geographic subdivision of the state used primarily for statistical and judicial purposes rather than local government.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:17 p.m.