Triple
T5608712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Bedford |
E147298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New England town |
C6195
|
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: New England town Context triple: [Town of Bedford, instanceOf, New England town]
-
A.
town in Massachusetts
chosen
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.
-
B.
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.
-
C.
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.
-
D.
New Englander
A New Englander is a person from the New England region of the northeastern United States, often associated with a distinct cultural identity shaped by the area's history, climate, and traditions.
-
E.
county in Massachusetts
A county in Massachusetts is an administrative and geographic subdivision of the state that historically provided local government functions, though many have since had their governmental powers reduced or abolished, serving primarily as regional boundaries for courts, law enforcement, and statistical purposes.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:39 p.m.