Triple

T285934
Position Surface form Disambiguated ID Type / Status
Subject Engineer Branch E5884 entity
Predicate instanceOf P0 FINISHED
Object combat support branch C298 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: combat support branch
Context triple: [Engineer Branch, instanceOf, combat support branch]
  • A. land warfare service branch
    A land warfare service branch is a military organization primarily responsible for conducting combat and support operations on land using ground forces and associated assets.
  • B. branch of the United States Army
    A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
  • C. military communications organization
    A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
  • D. military organization chosen
    A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
  • E. branch of the United States Armed Forces
    A branch of the United States Armed Forces is a distinct military service component (such as the Army, Navy, Air Force, Marine Corps, Space Force, or Coast Guard) with its own mission, structure, and responsibilities for national defense and security.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.