Triple
T23879099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Sasso raid |
E600149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special forces operation |
C340
|
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: special forces operation Context triple: [Gran Sasso raid, instanceOf, special forces operation]
-
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.
United States special forces raid
A United States special forces raid is a highly planned, time-sensitive military operation conducted by elite U.S. units to infiltrate hostile or denied areas, achieve a specific objective such as capturing or killing high-value targets, and exfiltrate rapidly with minimal collateral damage.
-
C.
special operations forces course
A special operations forces course is an intensive training program designed to develop elite military personnel in advanced combat skills, unconventional warfare, and high-risk mission execution.
-
D.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
special operations forces officer
A special operations forces officer is a highly trained military leader who plans, coordinates, and commands small, elite units in complex, high-risk missions often requiring unconventional tactics and specialized skills.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:23 p.m.