Triple
T34347060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod AEW3 |
E881463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne early warning and control aircraft project |
C61280
|
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 aircraft project Context triple: [Nimrod AEW3, instanceOf, airborne early warning and control aircraft project]
-
A.
anti-submarine warfare aircraft program
A coordinated initiative to design, develop, acquire, and sustain specialized aircraft, systems, and capabilities dedicated to detecting, tracking, and neutralizing submarine threats.
-
B.
maritime patrol aircraft program
A maritime patrol aircraft program is an organized effort to design, acquire, operate, and sustain aircraft and supporting systems dedicated to long-range surveillance, anti-submarine warfare, and protection of maritime domains.
-
C.
bomber aircraft project
A bomber aircraft project is a coordinated effort to design, develop, test, and produce an aircraft optimized for delivering explosive ordnance to ground or sea targets under specified operational requirements.
-
D.
airborne early warning squadron
An airborne early warning squadron is a military aviation unit equipped with specialized radar aircraft to detect, track, and relay information on aerial and surface threats, providing command and control support to friendly forces.
-
E.
X-plane
An X-plane is an experimental aircraft designed to test and demonstrate new aviation technologies, configurations, or performance capabilities beyond those of conventional aircraft.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.