Triple
T4791901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vessel Traffic Service Rotterdam |
E106621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime traffic management authority |
C4267
|
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 traffic management authority Context triple: [Vessel Traffic Service Rotterdam, instanceOf, maritime traffic management authority]
-
A.
maritime navigation authority
chosen
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 law enforcement activity
Maritime law enforcement activity is the set of actions by authorized agencies to monitor, control, and ensure compliance with laws and regulations in maritime zones, including preventing and responding to illegal activities at sea.
-
C.
International Maritime Organization instrument
An International Maritime Organization instrument is a formal legal or regulatory document—such as a convention, code, or guideline—adopted by the IMO to establish international standards for maritime safety, security, and environmental protection.
-
D.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
E.
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.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:22 p.m.