Triple
T33104170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HART |
E847141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency medical and rescue unit |
C4743
|
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 and rescue unit Context triple: [HART, instanceOf, emergency medical and rescue unit]
-
A.
rescue unit
chosen
A rescue unit is an organized team equipped and trained to respond rapidly to emergencies, providing aid, protection, and extraction of people or animals from dangerous or life-threatening situations.
-
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.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
-
E.
emergency services provider
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.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.