Triple
T15936724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Sea Commission |
E386458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional sea convention 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 sea convention body Context triple: [Black Sea Commission, instanceOf, regional sea convention body]
-
A.
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.
-
B.
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.
-
C.
maritime confederation
A maritime confederation is a loose alliance of seafaring states or cities that cooperate to control trade routes, naval defense, and maritime law while retaining their political independence.
-
D.
law of the sea institution
A law of the sea institution is an organization or body responsible for developing, interpreting, implementing, or enforcing legal rules and frameworks governing the use, management, and protection of the world’s oceans and marine resources.
-
E.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.