Triple
T27659592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Off-Highway Vehicle Program |
E697084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recreation management program |
C53110
|
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: recreation management program Context triple: [Off-Highway Vehicle Program, instanceOf, recreation management program]
-
A.
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.
-
B.
forest management program
A forest management program is an organized set of policies, practices, and monitoring activities designed to sustainably manage forest resources, balance ecological health with economic and social needs, and ensure long-term forest resilience.
-
C.
recreation area
A recreation area is a designated space, either natural or built, intended for leisure, relaxation, and recreational activities such as sports, picnicking, and social gatherings.
-
D.
recreational facility system
A recreational facility system is an integrated framework of spaces, equipment, services, and management processes designed to support and coordinate leisure, fitness, and community activities for users.
-
E.
conservation program component
A conservation program component is a distinct element—such as a project, activity, policy, or resource—within a broader conservation initiative that contributes specific functions or outcomes toward achieving environmental protection goals.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:35 p.m.