Triple
T13180337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erieye radar |
E313705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne early warning and control radar system |
C5345
|
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: airborne early warning and control radar system Context triple: [Erieye radar, instanceOf, airborne early warning and control radar system]
-
A.
airborne radar system
chosen
An airborne radar system is an integrated aircraft-mounted sensor suite that emits radio waves and processes their reflections to detect, track, and characterize objects or terrain in the surrounding air and ground environment.
-
B.
military radar system
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
-
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.
missile warning system
A missile warning system is a defense mechanism that detects, tracks, and alerts relevant entities to incoming missile threats to enable timely protective or countermeasure responses.
-
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.
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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.