Triple
T2927858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Pacific Fishery Management Council |
E78890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regional fishery management council |
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: Regional fishery management council Context triple: [North Pacific Fishery Management Council, instanceOf, Regional fishery management council]
-
A.
oceanographic organization
An oceanographic organization is an entity dedicated to studying, monitoring, and managing the oceans and marine environments through scientific research, data collection, and related educational or policy activities.
-
B.
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.
-
C.
Great Lakes management designation
A Great Lakes management designation is an official classification assigned to specific areas, waters, or resources within the Great Lakes region to guide their protection, use, and regulatory oversight.
-
D.
marine conservation center
A marine conservation center is a facility dedicated to protecting ocean ecosystems through research, education, wildlife rehabilitation, and community engagement.
-
E.
river basin organization
A river basin organization is an institutional body responsible for coordinating the management, development, and protection of water and related resources within a defined river basin across sectors and 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:55 p.m.