Triple
T33863405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riyadh Memorandum of Understanding on Port State Control |
E867979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional maritime agreement |
C61789
|
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 maritime agreement Context triple: [Riyadh Memorandum of Understanding on Port State Control, instanceOf, regional maritime agreement]
-
A.
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.
-
B.
maritime polity
A maritime polity is a political entity whose power, economy, and cultural identity are fundamentally organized around control of the sea, seafaring, and maritime trade routes.
-
C.
maritime boundary decision
A maritime boundary decision is a formal determination, typically by a court, tribunal, or negotiated agreement, that defines the spatial limits and legal rights of states over adjacent or overlapping maritime zones such as territorial seas, exclusive economic zones, and continental shelves.
-
D.
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.
-
E.
maritime border
A maritime border is a legally defined boundary at sea that separates the territorial waters, exclusive economic zones, or other maritime jurisdictions of neighboring states.
- F. None of above. chosen
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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.