Triple
T33179099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellington, Connecticut |
E849268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Connecticut |
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: municipality in Connecticut Context triple: [Ellington, Connecticut, instanceOf, municipality in Connecticut]
-
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.
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.
-
C.
municipality in New York
A municipality in New York is a legally incorporated local government entity—such as a city, town, or village—established under New York State law to provide public services and governance within a defined geographic area.
-
D.
municipality in Pennsylvania
A municipality in Pennsylvania is a legally defined local government entity—such as a city, borough, township, or town—responsible for providing public services and governance within its geographic boundaries in the state of Pennsylvania.
-
E.
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.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.