Triple

T26766576
Position Surface form Disambiguated ID Type / Status
Subject Armored Brigade Combat Team E674955 entity
Predicate instanceOf P0 FINISHED
Object heavy brigade combat team C30059 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: heavy brigade combat team
Context triple: [Armored Brigade Combat Team, instanceOf, heavy brigade combat team]
  • A. armored brigade combat team chosen
    An armored brigade combat team is a highly mobile, heavily armored combined-arms military formation designed to conduct offensive and defensive ground operations using tanks, mechanized infantry, artillery, and support units.
  • B. anti-tank battalion
    An anti-tank battalion is a military unit organized, equipped, and trained specifically to detect, engage, and destroy enemy armored vehicles and tanks using specialized anti-armor weapons and tactics.
  • C. airborne infantry brigade
    An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
  • D. assault gun brigade
    An assault gun brigade is a military formation equipped primarily with assault guns or self-propelled artillery, organized to provide direct fire support to infantry and armored units against enemy fortifications, armor, and strongpoints.
  • E. armored regiment
    An armored regiment is a military unit equipped primarily with tanks and other armored fighting vehicles, organized to conduct offensive and defensive ground combat 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_69eecda85298819097ee1c38a3d772e7 completed April 27, 2026, 2:44 a.m.
Created at: April 27, 2026, 4 a.m.