Triple
T33956476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 244th Sentai |
E870585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Japanese Army Air Force unit |
C60919
|
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 Air Force unit Context triple: [244th Sentai, instanceOf, Imperial Japanese Army Air Force unit]
-
A.
Japan Air Self-Defense Force unit
A Japan Air Self-Defense Force unit is an organizational entity within Japan’s air defense branch, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions.
-
B.
Japanese naval military police unit
A Japanese naval military police unit is a specialized law enforcement formation within the navy responsible for maintaining discipline, security, and order among naval personnel and installations.
-
C.
Luftwaffe fighter unit
A Luftwaffe fighter unit is a World War II-era German air force formation composed of fighter aircraft and their crews, organized to achieve air superiority, escort missions, and defensive operations.
-
D.
Japanese military administration unit
A Japanese military administration unit is an organizational entity within Japan’s armed forces responsible for managing logistics, personnel, planning, and support functions necessary to sustain military operations.
-
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. 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.