Triple
T8234085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-3.1 Allied Joint Maritime Operations |
E192361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime operations doctrine |
C23749
|
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 operations doctrine Context triple: [AJP-3.1 Allied Joint Maritime Operations, instanceOf, maritime operations doctrine]
-
A.
maritime command and control framework
A maritime command and control framework is an integrated structure of processes, technologies, and organizational roles that enables coordinated planning, decision-making, and execution of naval and maritime operations across multiple domains and stakeholders.
-
B.
maritime passage
A maritime passage is a navigable sea route or waterway that connects larger bodies of water, enabling the movement of ships and maritime traffic between regions.
-
C.
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.
-
D.
naval operational area
A naval operational area is a defined maritime region where naval forces conduct coordinated military activities, including movement, surveillance, training, and combat operations, under specific rules and command structures.
-
E.
maritime reference work
A maritime reference work is a comprehensive resource that compiles and organizes authoritative information about ships, navigation, seafaring practices, maritime law, and ocean-related subjects for quick consultation.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.