Triple

T35891556
Position Surface form Disambiguated ID Type / Status
Subject 620th Special Operations Battalion Baneasa-Otopeni E1037796 entity
Predicate instanceOf P0 FINISHED
Object Romanian Land Forces unit C19117 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: Romanian Land Forces unit
Context triple: [620th Special Operations Battalion Baneasa-Otopeni, instanceOf, Romanian Land Forces unit]
  • A. branch of the Romanian Armed Forces
    A branch of the Romanian Armed Forces is a major organizational component, such as the Land Forces, Air Force, or Naval Forces, responsible for specific types of military operations and capabilities within Romania’s national defense structure.
  • B. formation of the Romanian Land Forces chosen
    The formation of the Romanian Land Forces refers to the historical process through which Romania organized, structured, and developed its ground military units into a coherent national army responsible for land-based defense and operations.
  • C. subunit of the Romanian Gendarmerie
    A subunit of the Romanian Gendarmerie is an organizational component, such as a company, platoon, or specialized detachment, that performs specific public order, security, or intervention tasks under the command structure of the national gendarmerie.
  • D. Royal Hungarian Army unit
    A Royal Hungarian Army unit is a military formation of the Kingdom of Hungary’s land forces, organized for combat, support, or administrative purposes within the Royal Hungarian Army.
  • E. Panzerjäger unit
    A Panzerjäger unit is a specialized military formation equipped and trained primarily for hunting, engaging, and destroying enemy armored vehicles, especially tanks.
  • 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_69f76e1f4d748190bb55594d8441d70e completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:06 p.m.