Triple
T9100147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow emergency medical services |
E218130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-hospital care system |
C21507
|
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: pre-hospital care system Context triple: [Moscow emergency medical services, instanceOf, pre-hospital care system]
-
A.
public emergency service system
chosen
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.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
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.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
-
E.
hospital system facilities
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:15 p.m.