Triple
T16093623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Select Board and Town Meeting |
E390424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New England town government model |
C8884
|
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 government model Context triple: [Select Board and Town Meeting, instanceOf, New England town government model]
-
A.
system of local government
chosen
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
B.
civil township
A civil township is a local unit of government, typically a subdivision of a county, that provides administrative and public services to residents in rural or semi-rural areas.
-
C.
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.
-
D.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
E.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 4:59 a.m.