Triple
T4507312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleburg, Virginia |
E101363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Virginia |
C17046
|
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: municipality in Virginia Context triple: [Middleburg, Virginia, instanceOf, municipality in Virginia]
-
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.
neighborhood in Arlington County, Virginia
A neighborhood in Arlington County, Virginia is a localized residential and mixed-use area within the county’s boundaries, typically defined by shared community identity, land-use patterns, and geographic or infrastructural features.
-
C.
county of Maryland
A county of Maryland is a primary local government and administrative subdivision of the U.S. state of Maryland, responsible for providing regional services, governance, and regulation within its defined geographic boundaries.
-
D.
municipality in Missouri
A municipality in Missouri is an incorporated local government entity within the state of Missouri, such as a city, town, or village, that has legal authority to provide services and enact ordinances for its residents.
-
E.
town in North Carolina
A town in North Carolina is a municipally incorporated community within the state that provides local governance, services, and regulations for its residents under North Carolina law.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:01 p.m.