Triple
T14905230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Sport Fish |
E360112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fish and wildlife management agency division |
C2583
|
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: fish and wildlife management agency division Context triple: [Division of Sport Fish, instanceOf, fish and wildlife management agency division]
-
A.
fish and wildlife agency
chosen
A fish and wildlife agency is a governmental or tribal organization responsible for conserving, managing, and regulating fish, wildlife, and their habitats for ecological health and public benefit.
-
B.
wildlife management area
A wildlife management area is a designated tract of land or water managed primarily for the conservation, habitat protection, and regulated use of wildlife and natural resources.
-
C.
natural resources management agency
A natural resources management agency is an organization responsible for planning, regulating, and overseeing the sustainable use, conservation, and restoration of natural resources such as land, water, forests, wildlife, and minerals.
-
D.
conservation department
A conservation department is an organizational unit responsible for protecting, managing, and restoring natural resources, ecosystems, and biodiversity within a defined jurisdiction or scope.
-
E.
United States Forest Service region
A United States Forest Service region is a major administrative division of the USFS that oversees and coordinates the management of national forests, grasslands, and related resources within a specific multi-state geographic area.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 2:12 a.m.