Triple
T3509153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington County, Maine |
E74153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county 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: county of Maine Context triple: [Washington County, Maine, instanceOf, county 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.
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.
-
C.
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.
-
D.
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.
-
E.
county of Minnesota
A county of Minnesota is an administrative and geographic subdivision of the U.S. state of Minnesota that provides local government services, governance, and regional organization for its residents and communities.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.