Triple
T15083993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau-designated Maine counties |
E360222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of Maine |
C2766
|
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: subdivision of Maine Context triple: [United States Census Bureau-designated Maine counties, instanceOf, subdivision of Maine]
-
A.
county in Maine
chosen
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.
-
B.
township in Maine
A township in Maine is an unorganized or minimally organized geographic subdivision of a county, typically rural and sparsely populated, that lacks full municipal government and is administered largely at the county or state level.
-
C.
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.
-
D.
county of New Hampshire
A county of New Hampshire is an administrative subdivision of the state that serves as a regional unit for local governance, judicial administration, and public services.
-
E.
overseas territory subdivision
An overseas territory subdivision is an administrative division of a country located outside its mainland, typically subject to the sovereign state's authority while often possessing distinct legal, political, or cultural arrangements.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:03 a.m.