Triple
T4401241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strafford County, New Hampshire |
E93620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of New Hampshire |
C15921
|
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: county of New Hampshire Context triple: [Strafford County, New Hampshire, instanceOf, county of New Hampshire]
-
A.
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.
-
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.
county of Vermont
A county of Vermont is an administrative and geographic subdivision of the state of Vermont that serves as a regional unit for local governance, judicial administration, and statistical purposes.
-
D.
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.
-
E.
county of New Jersey
A county of New Jersey is a primary local government and administrative subdivision of the state, encompassing multiple municipalities and providing regional services such as law enforcement, courts, and infrastructure management.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:28 p.m.