Triple
T1039574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnuson–Stevens Fishery Conservation and Management Act |
E22440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fisheries management law |
C1116
|
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: fisheries management law Context triple: [Magnuson–Stevens Fishery Conservation and Management Act, instanceOf, fisheries management law]
-
A.
wildlife conservation law
Wildlife conservation law is the body of legal rules, regulations, and policies designed to protect wild animal species and their habitats, manage human impacts on ecosystems, and promote biodiversity for present and future generations.
-
B.
fish and wildlife agency
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.
-
C.
wildlife protection law
A wildlife protection law is a legal framework that regulates human activities to conserve wild animal and plant species, their habitats, and biodiversity, often through prohibitions, permits, and enforcement mechanisms.
-
D.
fisherman
A fisherman is a person who catches fish and other aquatic animals, typically for food, livelihood, or recreation, using tools such as rods, nets, or traps in various bodies of water.
-
E.
environmental governance instrument
chosen
An environmental governance instrument is a policy tool, mechanism, or institutional arrangement used by public or private actors to influence behaviors and decisions in order to protect, manage, or restore the environment.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.