Triple

T31671768
Position Surface form Disambiguated ID Type / Status
Subject Komatsu Limited E808289 entity
Predicate instanceOf P0 FINISHED
Object military equipment manufacturer C5343 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: military equipment manufacturer
Context triple: [Komatsu Limited, instanceOf, military equipment manufacturer]
  • A. defense company chosen
    A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
  • B. armoured fighting vehicle manufacturer
    An armoured fighting vehicle manufacturer is a company that designs, engineers, and produces military-grade, heavily protected combat vehicles such as tanks, infantry fighting vehicles, and armoured personnel carriers for armed forces and defense clients.
  • C. defense industry holding company
    A defense industry holding company is a corporate entity that owns and manages a portfolio of businesses involved in the research, development, production, and support of military and security-related products and services.
  • D. defense industry leader
    A defense industry leader is a high-level executive or organization that shapes strategic direction, drives innovation, and oversees the development and delivery of military and security solutions within the defense sector.
  • E. military equipment
    Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
  • 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_69f348dbeef4819080b446a7feb6340b completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:01 p.m.