Triple
T3717169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Typhoon FGR4 mission systems |
E81558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat aircraft mission system suite |
C14168
|
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: combat aircraft mission system suite Context triple: [Typhoon FGR4 mission systems, instanceOf, combat aircraft mission system suite]
-
A.
flight simulation facility
A flight simulation facility is a specialized environment equipped with advanced simulators and support systems that replicate real-world aircraft operations for pilot training, research, and systems testing.
-
B.
weapon system
A weapon system is an integrated set of components, technologies, and processes designed to detect, engage, and neutralize targets through the controlled application of force.
-
C.
air and missile defense interceptor
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
D.
naval combat system component
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.
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.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.