Triple
T30050194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippensburg Area EMS |
E763578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Emergency medical services provider |
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 services provider Context triple: [Shippensburg Area EMS, instanceOf, Emergency medical services provider]
-
A.
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.
-
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 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.
-
D.
emergency medical services regulatory agency
An emergency medical services regulatory agency is a governmental or authorized body that establishes, implements, and enforces standards, policies, and oversight for the operation, quality, and safety of prehospital and out-of-hospital emergency medical care systems.
-
E.
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.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:55 p.m.