Triple
T733287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick County, Maryland |
E14876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of Maryland |
C5403
|
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 Maryland Context triple: [Frederick County, Maryland, instanceOf, county of Maryland]
-
A.
county in Virginia
A county in Virginia is a primary local government and geographic subdivision of the Commonwealth of Virginia, responsible for providing regional services, administration, and governance to the communities within its boundaries.
-
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 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.
-
D.
county of West Virginia
A county of West Virginia is a primary administrative and political subdivision of the U.S. state of West Virginia, responsible for local governance, public services, and regional administration within its defined geographic boundaries.
-
E.
county of California
A county of California is a regional administrative division of the state that provides local government services, governance, and jurisdiction over a defined geographic area and its residents.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.