Triple
T19343788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Central Atlantic Fishery Commission |
E483821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional fishery body |
C11923
|
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 body Context triple: [Western Central Atlantic Fishery Commission, instanceOf, regional fishery body]
-
A.
fisheries management area
A fisheries management area is a designated geographic region of water where specific rules and measures are applied to regulate fishing activities and conserve aquatic resources.
-
B.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
C.
regional scientific body
A regional scientific body is an organization that coordinates, supports, and promotes scientific research, collaboration, and policy advice within a specific geographic region.
-
D.
Pacific Ocean regional body
A Pacific Ocean regional body is an organization or institution that coordinates cooperation, governance, and policy-making among countries and stakeholders within the Pacific Ocean region on shared issues such as environment, security, and economic development.
-
E.
regional body of an international organization
chosen
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.