Triple
T14274244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany Township, Maine |
E353873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | township in Maine |
C33693
|
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: township in Maine Context triple: [Albany Township, Maine, instanceOf, township in Maine]
-
A.
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.
-
B.
county in Maine
A county in Maine is an administrative subdivision of the state that encompasses multiple municipalities and unorganized territories, providing regional governance, judicial services, and certain public functions.
-
C.
township in Minnesota
A township in Minnesota is a local governmental subdivision of a county, typically rural or semi-rural, responsible for providing basic services and land-use governance within its defined geographic boundaries.
-
D.
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.
-
E.
township in Pennsylvania
A township in Pennsylvania is a type of municipal subdivision of a county that provides local government services to residents in areas that are typically less densely populated than cities or boroughs.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.