Triple
T24599903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritime Rescue Coordination Centre |
E608794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency operations centre |
C37844
|
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: emergency operations centre Context triple: [Maritime Rescue Coordination Centre, instanceOf, emergency operations centre]
-
A.
emergency management facility
chosen
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
-
B.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
C.
command and control centre
A command and control centre is a centralized facility where information is collected, analyzed, and used to coordinate and direct operations, resources, and decision-making in real time.
-
D.
police operations center
A police operations center is a centralized facility where law enforcement personnel monitor incidents, coordinate field units, manage communications, and make real-time decisions to ensure public safety and effective response.
-
E.
emergency management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
- 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.