Triple
T29454942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichtenstein radar family |
E747073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne interception radar family |
C14022
|
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 interception radar family Context triple: [Lichtenstein radar family, instanceOf, airborne interception radar family]
-
A.
radar system family
chosen
A radar system family is a group of related radar systems that share a common architecture, technology base, and design principles while differing in specific capabilities, configurations, or applications.
-
B.
airborne radar system
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.
-
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.
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.
-
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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:35 p.m.