Triple
T3255072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy West Africa Squadron enforcement |
E68276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime law enforcement activity |
C12562
|
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 law enforcement activity Context triple: [Royal Navy West Africa Squadron enforcement, instanceOf, maritime law enforcement activity]
-
A.
maritime navigation authority
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
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.
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.
-
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 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.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:09 p.m.