Triple
T31620302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Operations Response Team |
E806878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialist ambulance unit |
C37852
|
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: specialist ambulance unit Context triple: [Special Operations Response Team, instanceOf, specialist ambulance unit]
-
A.
specialist unit
A specialist unit is a dedicated organizational subgroup composed of experts and specialized resources focused on performing specific, complex, or high-priority tasks within a broader system or institution.
-
B.
ambulance variant
chosen
An ambulance variant is a specialized configuration of an emergency medical vehicle tailored with specific equipment, capacity, and design features to support particular medical, logistical, or environmental requirements.
-
C.
rescue unit
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.
-
D.
ambulance station
An ambulance station is a facility where ambulances and emergency medical personnel are housed, maintained, and dispatched to respond to medical emergencies.
-
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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:40 p.m.