Triple
T12329652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Boat Teams |
E293923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime special operations unit |
C10260
|
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 special operations unit Context triple: [Special Boat Teams, instanceOf, maritime special operations unit]
-
A.
specialized maritime unit
A specialized maritime unit is a dedicated team within a naval or coast guard organization trained and equipped to conduct specific high-skill missions at sea, such as search and rescue, interdiction, special operations, or environmental protection.
-
B.
naval special forces
chosen
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.
-
C.
maritime law enforcement unit
A maritime law enforcement unit is an organized body responsible for enforcing laws, ensuring security, and protecting resources within a nation’s territorial waters and maritime zones.
-
D.
Marine Corps special operations unit
A Marine Corps special operations unit is an elite, highly trained military formation specializing in direct action, special reconnaissance, and unconventional warfare in maritime and littoral environments.
-
E.
mine countermeasures force
A mine countermeasures force is a specialized naval unit equipped, trained, and organized to detect, classify, neutralize, and dispose of naval mines to ensure safe maritime 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.