Triple
T16965883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Chart Display and Information System |
E411538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime navigation system |
C2386
|
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 navigation system Context triple: [Electronic Chart Display and Information System, instanceOf, maritime navigation 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.
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.
-
C.
maritime convoy system
A maritime convoy system is an organized method of grouping merchant or military vessels to sail together under coordinated protection and navigation to reduce risks from threats such as enemy attacks, piracy, or hazardous conditions.
-
D.
terrestrial navigation system
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
-
E.
navigational aid
chosen
A navigational aid is a tool, device, or system that helps users determine their position and plan or follow a route from one location to another.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.