Triple

T10846974
Position Surface form Disambiguated ID Type / Status
Subject Hessian auxiliary corps in North America E256038 entity
Predicate instanceOf P0 FINISHED
Object early modern mercenary contingent C14976 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: early modern mercenary contingent
Context triple: [Hessian auxiliary corps in North America, instanceOf, early modern mercenary contingent]
  • A. mercenary chosen
    A mercenary is a professional soldier who offers combat services to the highest bidder, motivated primarily by payment rather than allegiance to a particular cause or nation.
  • B. 16th-century conflict
    A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
  • C. early modern state
    An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
  • D. Parliamentarian cavalry
    Parliamentarian cavalry were mounted troops loyal to the English Parliament during the Civil War, combining mobility, shock tactics, and disciplined formations to challenge Royalist forces on the battlefield.
  • E. elite troops
    Elite troops are highly trained, exceptionally skilled military units selected for their superior physical, mental, and tactical capabilities to perform the most demanding and critical missions.
  • 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_69d6aa81a5d08190aa86689061d1ddd2 completed April 8, 2026, 7:20 p.m.
Created at: April 8, 2026, 9:20 p.m.