Triple
T28080754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traffic Separation Scheme |
E709668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime traffic management system |
C53754
|
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 system Context triple: [Traffic Separation Scheme, instanceOf, maritime traffic management system]
-
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.
vessel tracking system
A vessel tracking system is a software and hardware solution that continuously monitors, records, and displays the real-time positions, movements, and statuses of maritime vessels for safety, logistics, and regulatory purposes.
-
C.
maritime navigation practice
Maritime navigation practice is the systematic application of techniques, tools, and procedures used by mariners to safely and efficiently plan, monitor, and adjust a vessel’s course at sea.
-
D.
maritime security infrastructure
Maritime security infrastructure encompasses the integrated systems, facilities, technologies, and organizational frameworks designed to protect maritime domains, ports, and shipping routes from threats, ensure safe navigation, and support law enforcement and emergency response at sea.
-
E.
maritime convoy system
A maritime convoy system is an organized method of grouping and coordinating multiple ships under shared routing, scheduling, and protection protocols to enhance safety, security, and efficiency during sea transit.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:51 p.m.