Triple
T7013612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armonk Volunteer Ambulance Corps |
E162644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency medical services organization |
C437
|
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 organization Context triple: [Armonk Volunteer Ambulance Corps, instanceOf, emergency medical services organization]
-
A.
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.
-
B.
medical organization
chosen
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
C.
emergency management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
-
D.
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.
-
E.
crisis response organization
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:34 p.m.