Triple
T35446216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do 335 A-6 |
E1024492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconnaissance aircraft project |
C4000
|
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: reconnaissance aircraft project Context triple: [Do 335 A-6, instanceOf, reconnaissance aircraft project]
-
A.
reconnaissance aircraft
chosen
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
-
B.
military aircraft project
A military aircraft project is an organized effort to design, develop, test, and produce an aircraft intended for defense or combat roles, encompassing technical, logistical, financial, and strategic considerations.
-
C.
airborne early warning and control aircraft project
An airborne early warning and control aircraft project is a coordinated effort to design, develop, and integrate an aircraft equipped with advanced radar, sensors, and communication systems to detect, track, and manage air and surface threats while providing command and control capabilities.
-
D.
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.
-
E.
unbuilt aircraft project
An unbuilt aircraft project is a conceptual or proposed airplane design that was planned and possibly studied or partially developed but never constructed or flown.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.