Triple
T14281436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Control Unit |
E354056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coast guard–type unit |
C24532
|
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: coast guard–type unit Context triple: [Coastal Control Unit, instanceOf, coast guard–type unit]
-
A.
United States Coast Guard unit
A United States Coast Guard unit is an organized group within the Coast Guard, such as a cutter, station, air station, or specialized team, that performs specific missions related to maritime safety, security, and environmental protection.
-
B.
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.
-
C.
maritime law enforcement unit
chosen
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.
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.
-
E.
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.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.