Triple

T6325260
Position Surface form Disambiguated ID Type / Status
Subject Combat Applications Group E141847 entity
Predicate instanceOf P0 FINISHED
Object special operations forces unit 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 operations forces unit
Context triple: [Combat Applications Group, instanceOf, special operations forces unit]
  • A. 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.
  • B. 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.
  • C. special operations aviation regiment
    A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
  • D. specialized operations division
    A specialized operations division is a focused organizational unit responsible for planning and executing complex, high-priority, or technically advanced missions that fall outside the scope of standard operational teams.
  • E. Marine Corps special operations unit
    A Marine Corps special operations unit is an elite, highly trained military formation specializing in direct action, special reconnaissance, and unconventional warfare in maritime and littoral environments.
  • F. None of above. chosen

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_69c008d201748190917e69c41ba3f978 completed March 22, 2026, 3:20 p.m.
Created at: March 22, 2026, 4:29 p.m.