Triple
T8606220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatzalah volunteer ambulance service |
E203804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency medical service |
C24711
|
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 medical service Context triple: [Hatzalah volunteer ambulance service, instanceOf, emergency medical 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.
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.
air medical service provider
An air medical service provider is an organization that operates aircraft equipped and staffed to deliver emergency or critical medical care and transport patients between locations.
-
D.
medical contingent
A medical contingent is a group of healthcare professionals and support staff organized to provide medical services and emergency care in a specific location, event, or operational context.
-
E.
public health emergency
A public health emergency is a situation in which the health of a population is threatened by a significant, often rapidly spreading hazard (such as an infectious disease, environmental exposure, or bioterrorism event) that requires urgent, coordinated public health action and resource mobilization.
- F. None of above. chosen
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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.