Triple
T3371011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritime Authority System |
E70953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime command and control framework |
C12676
|
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 command and control framework Context triple: [Maritime Authority System, instanceOf, maritime command and control framework]
-
A.
naval combat system component
A naval combat system component is an individual hardware or software element—such as a sensor, weapon, processor, or communication module—that contributes specific functionality to the detection, tracking, engagement, or control capabilities of an integrated maritime warfare system.
-
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.
United States Navy systems command
The United States Navy systems command is an organizational entity responsible for developing, acquiring, and sustaining specific categories of naval systems, equipment, and technologies in support of fleet operations.
-
E.
maritime security process
A maritime security process is a coordinated set of policies, procedures, and actions designed to prevent, detect, and respond to threats and unlawful activities in maritime domains to protect vessels, ports, cargo, 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.