Triple

T37028314
Position Surface form Disambiguated ID Type / Status
Subject ARUR-13 ESM system E916416 entity
Predicate instanceOf P0 FINISHED
Object naval electronic warfare system C1870 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: naval electronic warfare system
Context triple: [ARUR-13 ESM system, instanceOf, naval electronic warfare system]
  • A. 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.
  • B. naval missile system
    A naval missile system is an integrated shipborne weapon platform designed to detect, track, and engage air, surface, or subsurface threats using guided missiles coordinated by sensors and fire-control systems.
  • C. defensive avionics system
    A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
  • D. naval combat system component chosen
    A naval combat system component is an individual hardware or software element—such as a sensor, weapon, processor, or communication module—that contributes specific functionality to the detection, tracking, engagement, or control capabilities of an integrated maritime warfare system.
  • E. electronic warfare command
    An electronic warfare command is an organizational unit responsible for planning, coordinating, and executing operations that use the electromagnetic spectrum to detect, disrupt, deceive, or protect against adversary electronic systems.
  • 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_69f76e92c7648190bcfa277f64c71a21 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:14 p.m.