Triple
T8205382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part D – Sound and Light Signals |
E191674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of international maritime regulations |
C3137
|
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: section of international maritime regulations Context triple: [Part D – Sound and Light Signals, instanceOf, section of international maritime regulations]
-
A.
International Maritime Organization instrument
chosen
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.
-
B.
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.
-
C.
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.
-
D.
navigation law
Navigation law is a legal framework governing the rights, responsibilities, and regulations related to the movement of vessels, aircraft, or vehicles through maritime, air, or other navigable spaces.
-
E.
maritime designation
A maritime designation is a formal label or classification assigned to ships, sea areas, routes, or maritime activities to define their status, function, or regulatory conditions.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:43 p.m.