Triple
T7597406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichiki Detachment |
E179891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese military unit |
C2497
|
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: Japanese military unit Context triple: [Ichiki Detachment, instanceOf, Japanese military unit]
-
A.
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.
-
B.
Imperial Japanese Army institution
An Imperial Japanese Army institution is an organizational entity—such as a school, bureau, or research center—established to train personnel, develop doctrine, manage logistics, or support the operational and administrative functions of the Imperial Japanese Army.
-
C.
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.
-
D.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:53 p.m.