Triple
T21958840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi A7M Reppū |
E542266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II Japanese fighter project |
C42756
|
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: World War II Japanese fighter project Context triple: [Mitsubishi A7M Reppū, instanceOf, World War II Japanese fighter project]
-
A.
Japanese fighter aircraft development program
chosen
A Japanese fighter aircraft development program is an organized, government- and industry-led effort to research, design, test, and produce new generations of combat aircraft to meet Japan’s strategic, technological, and defense requirements.
-
B.
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.
-
C.
World War II aircraft
World War II aircraft are military airplanes designed, produced, and deployed between 1939 and 1945 for roles such as fighters, bombers, transports, and reconnaissance in support of the war’s air operations.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
E.
Japanese Navy aircraft
Japanese Navy aircraft are military airplanes and seaplanes designed, operated, or procured by Japan’s naval forces for roles such as air superiority, maritime patrol, anti-ship and anti-submarine warfare, reconnaissance, and support.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8 p.m.