Triple
T6707749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | División de Fuerzas Especiales |
E153050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special forces formation |
C20321
|
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 formation Context triple: [División de Fuerzas Especiales, instanceOf, special forces formation]
-
A.
special operations forces unit
chosen
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.
army formation
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
C.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
-
D.
air force formation
An air force formation is an organized arrangement of multiple military aircraft flying together in a coordinated pattern to achieve tactical, strategic, or ceremonial objectives.
-
E.
Royal Marines formation
A Royal Marines formation is an organized, mission-tailored military unit of the Royal Marines, structured and equipped to conduct amphibious, littoral, and expeditionary operations under a unified command.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:06 p.m.