Triple

T8855721
Position Surface form Disambiguated ID Type / Status
Subject Hungarian Territorial Defence Forces E210751 entity
Predicate instanceOf P0 FINISHED
Object component of the Hungarian Defence Forces C25199 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: component of the Hungarian Defence Forces
Context triple: [Hungarian Territorial Defence Forces, instanceOf, component of the Hungarian Defence Forces]
  • A. military unit
    A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
  • B. branch of the Bundeswehr
    A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
  • C. component of land forces
    A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
  • D. component of the United States Army
    A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
  • E. component of the Australian Army
    A component of the Australian Army is an organizational subdivision—such as a unit, formation, corps, or support element—that contributes specific capabilities and functions to the Army’s overall mission and operations.
  • F. None of above. chosen

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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 6:49 p.m.