Triple

T13762839
Position Surface form Disambiguated ID Type / Status
Subject Kokura Arsenal E330657 entity
Predicate instanceOf P0 FINISHED
Object Imperial Japanese Army arsenal C9010 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 arsenal
Context triple: [Kokura Arsenal, instanceOf, Imperial Japanese Army arsenal]
  • A. 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.
  • B. Imperial Japanese Army area army
    An Imperial Japanese Army area army was a high-level regional military command responsible for coordinating and directing multiple field armies within a designated theater of operations.
  • C. 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.
  • 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. armory chosen
    An armory is a secure facility or room where weapons, armor, and related military equipment are stored, maintained, and sometimes issued.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:10 p.m.