Triple
T4078733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Group on the State of the Environment and Nature Conservation |
E87426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional marine protection body |
C4322
|
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 marine protection body Context triple: [Working Group on the State of the Environment and Nature Conservation, instanceOf, regional marine protection body]
-
A.
marine conservation center
A marine conservation center is a facility dedicated to protecting ocean ecosystems through research, education, wildlife rehabilitation, and community engagement.
-
B.
marine ecoregion
A marine ecoregion is a geographically distinct area of ocean or coastal waters characterized by a relatively homogeneous community of species, environmental conditions, and ecological processes.
-
C.
United States national marine sanctuary
A United States national marine sanctuary is a federally designated protected area of ocean or Great Lakes waters managed to conserve natural and cultural resources while supporting compatible public use, research, and education.
-
D.
oceanographic organization
chosen
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.
-
E.
maritime zone
A maritime zone is a legally defined area of the sea, measured from a coastal state's baseline, within which specific rights, jurisdiction, and responsibilities are allocated under international law.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.