Triple
T21158183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Coast Guard |
E521365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coast guard service |
C13810
|
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 service Context triple: [Canadian Coast Guard, instanceOf, coast guard service]
-
A.
coast guard
chosen
A coast guard is a maritime security and safety organization responsible for enforcing laws, conducting search and rescue, and protecting coastal waters and resources.
-
B.
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.
-
C.
U.S. Coast Guard directive
A U.S. Coast Guard directive is an official, authoritative document that establishes or communicates policies, procedures, responsibilities, or guidance for Coast Guard operations and administration.
-
D.
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.
-
E.
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.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:59 p.m.