Triple
T23408201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikugun Honjo Hifukusho |
E559992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese Army depot |
C16869
|
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 Army depot Context triple: [Rikugun Honjo Hifukusho, instanceOf, Japanese Army depot]
-
A.
Imperial Japanese Army position
An Imperial Japanese Army position is a specific military role or rank within the land forces of the Empire of Japan, defining an individual's authority, responsibilities, and place in the army hierarchy.
-
B.
Japan Air Self-Defense Force base
A Japan Air Self-Defense Force base is a military installation in Japan that supports the operation, training, maintenance, and command of the nation’s air defense and related missions.
-
C.
Japanese military administration unit
chosen
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.
-
D.
Japan Ground Self-Defense Force unit
A Japan Ground Self-Defense Force unit is an organized, mission-specific formation of personnel and equipment within Japan’s land-based military, structured to conduct defense, security, and support operations under national and international mandates.
-
E.
munitions facility
A munitions facility is an industrial site where explosive weapons, ammunition, and related components are manufactured, assembled, stored, and sometimes tested under controlled conditions.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:38 p.m.