Triple
T2068554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakajima Ki-27 |
E45962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Japanese Army aircraft |
C2492
|
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: Imperial Japanese Army aircraft Context triple: [Nakajima Ki-27, instanceOf, Imperial Japanese Army aircraft]
-
A.
military aircraft
chosen
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.
-
B.
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.
-
C.
Imperial Japanese Navy warship
An Imperial Japanese Navy warship is a naval combat vessel that served under Japan’s maritime military forces, primarily during the late 19th and early 20th centuries, designed and equipped for roles such as fleet engagement, escort, and power projection.
-
D.
Soviet aircraft
Soviet aircraft are military and civilian airplanes and helicopters designed, produced, or operated by the Soviet Union, reflecting its technological, strategic, and industrial priorities from 1922 to 1991.
-
E.
Imperial Japanese Navy institution
An Imperial Japanese Navy institution is an organized body, such as a naval academy, staff college, research bureau, or administrative office, that supported the training, planning, governance, and operational effectiveness of the Imperial Japanese Navy.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:41 p.m.