Triple
T2820177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeastern Connecticut |
E54387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Connecticut |
C143
|
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: region of Connecticut Context triple: [Northeastern Connecticut, instanceOf, region of Connecticut]
-
A.
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.
-
B.
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.
-
C.
region of the United States
chosen
A region of the United States is a geographically or culturally defined area within the country that shares common characteristics such as climate, history, economy, or social identity.
-
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.
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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:59 p.m.