Triple
T24599902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritime Rescue Coordination Centre |
E608794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | search and rescue coordination centre |
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: search and rescue coordination centre Context triple: [Maritime Rescue Coordination Centre, instanceOf, search and rescue coordination centre]
-
A.
maritime search and rescue region
A maritime search and rescue region is a defined sea area in which a specific authority is responsible for coordinating and conducting search and rescue operations for persons in distress.
-
B.
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.
-
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.
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.
-
E.
tsunami warning coordination body
A tsunami warning coordination body is an organization responsible for detecting tsunami threats, issuing timely alerts, and coordinating communication and response efforts among authorities, emergency services, and the public.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:30 a.m.