Triple
T3896660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Force |
E90387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-range penetration commando force |
C10260
|
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: long-range penetration commando force Context triple: [Special Force, instanceOf, long-range penetration commando force]
-
A.
long-range land-attack missile
A long-range land-attack missile is a guided weapon system designed to strike fixed or relocatable targets deep inland from significant stand-off distances, typically launched from air, sea, or ground platforms.
-
B.
long-range guided rocket weapon
A long-range guided rocket weapon is a self-propelled projectile system designed to accurately strike distant targets using onboard guidance and control technologies.
-
C.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
D.
naval special forces
chosen
Naval special forces are elite military units trained and equipped to conduct specialized maritime, amphibious, and coastal operations, often involving reconnaissance, direct action, and counterterrorism in and from the sea.
-
E.
special weapons and tactics unit
A special weapons and tactics unit is a highly trained law enforcement team equipped and organized to handle high-risk operations such as hostage rescues, armed standoffs, and counterterrorism incidents beyond the capabilities of regular police patrols.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.