Triple

T14786698
Position Surface form Disambiguated ID Type / Status
Subject Marinekommandoamt E347544 entity
Predicate instanceOf P0 FINISHED
Object naval command office C4787 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: naval command office
Context triple: [Marinekommandoamt, instanceOf, naval command office]
  • A. naval administrative office
    A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
  • B. naval office chosen
    A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
  • C. naval component command
    A naval component command is a subordinate joint force command responsible for planning, directing, and coordinating naval operations within a designated theater or area of responsibility.
  • D. naval command structure
    A naval command structure is the hierarchical organization of authority, responsibility, and communication within a navy that directs the planning, coordination, and execution of maritime operations.
  • E. United States Navy systems command
    The United States Navy systems command is an organizational entity responsible for developing, acquiring, and sustaining specific categories of naval systems, equipment, and technologies in support of fleet 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_69d822e9b9e08190bedcc31a163fda82 completed April 9, 2026, 10:06 p.m.
Created at: April 10, 2026, 1:31 a.m.