Triple
T8702406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Maritime Forces |
E206562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime security coalition |
C24908
|
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: maritime security coalition Context triple: [Combined Maritime Forces, instanceOf, maritime security coalition]
-
A.
maritime security code
A maritime security code is a set of international or national regulations and standards designed to prevent, detect, and respond to security threats against ships, ports, and maritime infrastructure.
-
B.
maritime security role
A maritime security role is a position responsible for protecting vessels, ports, and maritime infrastructure from threats such as piracy, terrorism, smuggling, and unauthorized access through surveillance, risk assessment, and enforcement measures.
-
C.
maritime security process
A maritime security process is a coordinated set of policies, procedures, and actions designed to prevent, detect, and respond to threats and unlawful activities in maritime domains to protect vessels, ports, cargo, and maritime infrastructure.
-
D.
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.
-
E.
maritime law enforcement unit
A maritime law enforcement unit is an organized body responsible for enforcing laws, ensuring security, and protecting resources within a nation’s territorial waters and maritime zones.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.