Triple
T27590163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Aodh |
E699773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | alarming service |
C3917
|
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: alarming service Context triple: [OpenStack Aodh, instanceOf, alarming service]
-
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.
разузнавателна служба
Разузнавателна служба е организация, която събира, анализира и използва информация за потенциални заплахи и интереси на държавата с цел защита на националната сигурност и подпомагане на вземането на стратегически решения.
-
C.
civil emergency service
A civil emergency service is a public organization responsible for preparing for, responding to, and managing non-military crises and disasters to protect people, property, and the environment.
-
D.
public warning system
chosen
A public warning system is an organized infrastructure of technologies, protocols, and communication channels designed to rapidly alert and inform the public about imminent or ongoing emergencies and hazards.
-
E.
emergency services provider
An emergency services provider is an organization or individual that delivers urgent, often life-saving assistance in response to crises, accidents, or disasters, such as medical emergencies, fires, or public safety threats.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:05 p.m.