Triple
T34044898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easements Program |
E873060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | easement-holding program |
C48540
|
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: easement-holding program Context triple: [Easements Program, instanceOf, easement-holding program]
-
A.
rural land management program
A rural land management program is an organized set of policies, practices, and support services designed to guide the sustainable use, conservation, and development of rural land and natural resources.
-
B.
recreation management program
A recreation management program is an organized course of study or system designed to plan, administer, and evaluate recreational activities, facilities, and services for diverse communities or organizations.
-
C.
land conservation program
chosen
A land conservation program is an organized initiative that protects, manages, and restores natural or working lands to preserve ecological, cultural, and recreational values for current and future generations.
-
D.
trail management program
A trail management program is a coordinated system of policies, tools, and activities used to plan, maintain, monitor, and improve recreational trails for safety, sustainability, and user experience.
-
E.
federal conservation program suite
A federal conservation program suite is an integrated set of government-administered initiatives, policies, and funding mechanisms designed to protect, restore, and sustainably manage natural resources and ecosystems across jurisdictions.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.