Triple
T9710399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish Border Guard |
E235008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime search and rescue organization |
C4341
|
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 search and rescue organization Context triple: [Finnish Border Guard, instanceOf, maritime search and rescue organization]
-
A.
sea rescue service
chosen
A sea rescue service is an organized maritime agency responsible for locating, assisting, and saving people, vessels, and property in distress at sea.
-
B.
maritime rescue device
A maritime rescue device is equipment specifically designed to aid in locating, supporting, and safely recovering people in distress at sea or other navigable waters.
-
C.
maritime navigation authority
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
D.
marine accident investigation body
A marine accident investigation body is an independent authority responsible for examining maritime incidents to determine causes, identify safety issues, and recommend measures to prevent future occurrences.
-
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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.