Triple
T29465468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing (gunship conversion) |
E747365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aircraft conversion program |
C55644
|
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: military aircraft conversion program Context triple: [Boeing (gunship conversion), instanceOf, military aircraft conversion program]
-
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.
U.S. Army aviation program
The U.S. Army aviation program encompasses the development, training, operation, and maintenance of rotary- and fixed-wing aircraft to provide air mobility, reconnaissance, attack, and support capabilities for Army missions.
-
C.
military aircraft
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
D.
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.
-
E.
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.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:52 p.m.