Triple
T12329602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVSPECWARCOM |
E293922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval special operations command |
C11385
|
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: naval special operations command Context triple: [NAVSPECWARCOM, instanceOf, naval special operations command]
-
A.
naval special forces
Naval special forces are elite military units trained and equipped to conduct specialized maritime, amphibious, and coastal operations, often involving reconnaissance, direct action, and counterterrorism in and from the sea.
-
B.
naval security force
A naval security force is a specialized military unit responsible for protecting naval assets, personnel, and infrastructure from threats through law enforcement, anti-terrorism, and force protection operations at sea and in port.
-
C.
military special operations command
chosen
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
D.
naval support services company
A naval support services company provides specialized operational, logistical, maintenance, and technical services to naval and maritime organizations to ensure the readiness, safety, and efficiency of their fleets and related infrastructure.
-
E.
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.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.