Triple
T5006999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Coast Guard Cyber Command |
E112521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Coast Guard unit |
C16787
|
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: United States Coast Guard unit Context triple: [U.S. Coast Guard Cyber Command, instanceOf, United States Coast Guard unit]
-
A.
United States Coast Guard facility
A United States Coast Guard facility is a designated site, such as a station, base, or support installation, used to house personnel, equipment, and operations that support the Coast Guard’s maritime safety, security, law enforcement, and environmental protection missions.
-
B.
United States Coast Guard cutter
A United States Coast Guard cutter is a commissioned vessel, typically 65 feet or longer, used by the Coast Guard for missions such as search and rescue, law enforcement, environmental protection, and national defense in U.S. waters and beyond.
-
C.
coast guard
A coast guard is a maritime security and safety organization responsible for enforcing laws, conducting search and rescue, and protecting coastal waters and resources.
-
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. 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.