Triple
T24080558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesapeake Forest Lands |
E596491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | publicly managed land |
C26564
|
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: publicly managed land Context triple: [Chesapeake Forest Lands, instanceOf, publicly managed land]
-
A.
common land
Common land is a shared area of land over which multiple people hold traditional or legal rights to use resources such as grazing, wood, or passage, even if the land is privately or publicly owned.
-
B.
land management agency
A land management agency is an organization responsible for planning, regulating, and overseeing the use, conservation, and development of public or private land resources.
-
C.
landscape management partnership
A landscape management partnership is a collaborative arrangement among diverse stakeholders—such as landowners, communities, governments, and NGOs—to plan, coordinate, and implement sustainable practices across a shared landscape for ecological, economic, and social benefits.
-
D.
public lands
chosen
Public lands are areas of land and natural resources owned collectively by the public and managed by government agencies for purposes such as conservation, recreation, resource extraction, and cultural or historical preservation.
-
E.
privately managed park
A privately managed park is a recreational green space owned or operated by a non-governmental entity that controls access, maintenance, and permitted activities, often funded through fees, memberships, or private investment.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:43 p.m.