Triple
T31620397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambulance Control Centres |
E806880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Emergency medical dispatch centre |
C48585
|
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 dispatch centre Context triple: [Ambulance Control Centres, instanceOf, Emergency medical dispatch centre]
-
A.
emergency medical service
Emergency medical service is a coordinated system that provides urgent pre-hospital assessment, treatment, and transportation for individuals experiencing acute illness or injury.
-
B.
emergency medical services facility
An emergency medical services facility is a specialized healthcare site equipped and staffed to provide immediate assessment, stabilization, and life-saving treatment to patients with urgent or critical medical conditions.
-
C.
emergency services provider
chosen
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.
-
D.
emergency management facility
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
-
E.
emergency services district
An emergency services district is a defined geographic area governed by a special-purpose local authority that organizes, funds, and oversees emergency response services such as fire protection, EMS, and rescue operations for the communities within its boundaries.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:40 p.m.