Triple

T13945485
Position Surface form Disambiguated ID Type / Status
Subject 59th (Wessex) Anti-Tank Regiment, Royal Artillery E335370 entity
Predicate instanceOf P0 FINISHED
Object artillery regiment of the British Army C21082 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: artillery regiment of the British Army
Context triple: [59th (Wessex) Anti-Tank Regiment, Royal Artillery, instanceOf, artillery regiment of the British Army]
  • A. artillery unit chosen
    An artillery unit is a military formation equipped with long-range weapons designed to deliver indirect fire support against enemy targets from protected or distant positions.
  • B. artillery corps
    An artillery corps is a military formation specialized in operating heavy weapons such as cannons, howitzers, and rocket systems to deliver long-range indirect fire support on the battlefield.
  • C. artillery battery
    An artillery battery is a military unit composed of multiple artillery pieces, their crews, and supporting equipment, organized to deliver coordinated indirect fire on designated targets.
  • D. British Army organizational element
    A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
  • E. British Army infantry regiment
    A British Army infantry regiment is a historic, regionally or culturally affiliated military unit responsible for recruiting, training, and organizing soldiers into battalions for frontline ground combat and related duties.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:17 p.m.