Triple
T30122344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMG1 |
E765592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Standing NATO Maritime Group |
C38973
|
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: Standing NATO Maritime Group Context triple: [SNMG1, instanceOf, Standing NATO Maritime Group]
-
A.
NATO maritime headquarters
chosen
A NATO maritime headquarters is a command-and-control organization responsible for planning, coordinating, and directing multinational naval operations and maritime security activities within an assigned area or mission.
-
B.
maritime security formation
A maritime security formation is an organized grouping of naval and coast guard assets coordinated to protect sea lanes, coastal areas, and maritime interests from threats such as piracy, terrorism, smuggling, and unauthorized incursions.
-
C.
maritime security coalition
A maritime security coalition is a collaborative alliance of nations, organizations, and agencies that coordinate resources, intelligence, and operations to protect sea lanes, deter threats, and uphold maritime law and safety.
-
D.
NATO personnel
NATO personnel are individuals serving in military, civilian, or support roles within the North Atlantic Treaty Organization, responsible for implementing its collective defense, crisis management, and cooperative security missions.
-
E.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.