Triple
T4064765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Virginia Regional Park Authority |
E86298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional park authority |
C1997
|
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: regional park authority Context triple: [Northern Virginia Regional Park Authority, instanceOf, regional park authority]
-
A.
parks and recreation agency
A parks and recreation agency is a public or private organization responsible for planning, managing, and providing recreational facilities, programs, and green spaces to enhance community well-being and environmental stewardship.
-
B.
national park authority
A national park authority is a governmental or designated public body responsible for managing, protecting, and promoting the sustainable use and enjoyment of a country's national parks and their natural and cultural resources.
-
C.
park district
chosen
A park district is a local governmental or administrative entity responsible for planning, developing, maintaining, and operating public parks, recreational facilities, and related community programs within a defined geographic area.
-
D.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
E.
county park
A county park is a publicly accessible natural or recreational area owned and managed by a county government, providing outdoor spaces, facilities, and activities for community use.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.