Triple
T17659953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Medical Services division |
E440222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Specialized unit |
C25280
|
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: Specialized unit Context triple: [Emergency Medical Services division, instanceOf, Specialized unit]
-
A.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
B.
specialist unit
chosen
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.
-
C.
SS special unit
A highly trained, elite military or paramilitary formation within the SS, organized for specialized missions such as reconnaissance, sabotage, counterinsurgency, or high-risk combat operations.
-
D.
specialized maritime unit
A specialized maritime unit is a dedicated team within a naval or coast guard organization trained and equipped to conduct specific high-skill missions at sea, such as search and rescue, interdiction, special operations, or environmental protection.
-
E.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 9:40 a.m.