Triple

T35780702
Position Surface form Disambiguated ID Type / Status
Subject Close-In Weapon System E1034429 entity
Predicate instanceOf P0 FINISHED
Object point-defense system C62274 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: point-defense system
Context triple: [Close-In Weapon System, instanceOf, point-defense system]
  • A. ground-based air defense system
    A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
  • B. naval defense system
    A naval defense system is an integrated network of sensors, weapons, platforms, and command-and-control components designed to detect, deter, and neutralize maritime threats to ships, fleets, and coastal assets.
  • C. integrated air defence system
    An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
  • D. coastal defense missile system
    A coastal defense missile system is a land-based military installation designed to detect, track, and engage hostile naval targets approaching a nation's shoreline using guided missiles and integrated sensor networks.
  • E. missile defense program
    A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
  • 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_69f76e14a1e081908eddd57bd6fdb3be completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:06 p.m.