Triple
T22583519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcelona Convention |
E564723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional seas convention |
C31387
|
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 seas convention Context triple: [Barcelona Convention, instanceOf, regional seas convention]
-
A.
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.
-
B.
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.
-
C.
law of the sea instrument
A law of the sea instrument is a formal legal document—such as a treaty, convention, or agreement—that establishes rules and principles governing the use, rights, and responsibilities of states and other actors in maritime spaces.
-
D.
maritime search and rescue region
A maritime search and rescue region is a defined sea area in which a specific authority is responsible for coordinating and conducting search and rescue operations for persons in distress.
-
E.
regional organisation
chosen
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.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:41 p.m.