Triple

T27687253
Position Surface form Disambiguated ID Type / Status
Subject schwere Panzerjäger-Abteilung 653 E698064 entity
Predicate instanceOf P0 FINISHED
Object tank destroyer battalion C29053 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: tank destroyer battalion
Context triple: [schwere Panzerjäger-Abteilung 653, instanceOf, tank destroyer battalion]
  • A. anti-tank battalion chosen
    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.
  • B. anti-tank regiment
    An anti-tank regiment is a military unit organized, equipped, and trained specifically to detect, engage, and destroy enemy armored vehicles and tanks, typically using specialized guns, missiles, and support systems.
  • C. anti-tank unit
    An anti-tank unit is a military formation equipped, trained, and organized specifically to detect, engage, and destroy enemy armored vehicles and tanks.
  • D. Waffen-SS heavy tank battalion
    A Waffen-SS heavy tank battalion was a specialized World War II German armored unit equipped primarily with heavy tanks like the Tiger, organized to deliver concentrated breakthrough and counterattack power in support of SS corps and army operations.
  • E. airborne anti-tank unit
    An airborne anti-tank unit is a highly mobile, air-deployable military formation equipped and trained to rapidly engage and destroy enemy armored vehicles behind or ahead of front lines.
  • 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_69ef590df8708190af5488f0638e790c completed April 27, 2026, 12:39 p.m.
Created at: April 27, 2026, 2:50 p.m.