Triple
T28711263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Search and Rescue Satellite-Aided Tracking payload |
E729837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | search and rescue system |
C22284
|
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 system Context triple: [Search and Rescue Satellite-Aided Tracking payload, instanceOf, search and rescue system]
-
A.
public emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
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.
public safety system
chosen
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
-
D.
sea rescue service
A sea rescue service is an organized maritime agency responsible for locating, assisting, and saving people, vessels, and property in distress at sea.
-
E.
cooperative surveillance system
A cooperative surveillance system is a network of distributed sensors, platforms, and agents that share and fuse information in real time to achieve more comprehensive, accurate, and resilient monitoring than any individual component could provide alone.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:48 a.m.