Triple
T7332544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leesburg Historic District |
E169038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic district in Virginia |
C11600
|
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: historic district in Virginia Context triple: [Leesburg Historic District, instanceOf, historic district in Virginia]
-
A.
municipality in Virginia
A municipality in Virginia is a legally incorporated local government entity, such as a city or town, within the Commonwealth of Virginia that provides public services and exercises governmental authority over a defined geographic area.
-
B.
historic district in Florida
A historic district in Florida is a geographically defined area recognized for its concentration of buildings, structures, and sites that reflect the architectural, cultural, and historical heritage of the state, often protected through local, state, or national preservation programs.
-
C.
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.
-
D.
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.
-
E.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:03 p.m.