Triple

T3899186
Position Surface form Disambiguated ID Type / Status
Subject War of the League of Cognac E90443 entity
Predicate instanceOf P0 FINISHED
Object 16th-century conflict C14531 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: 16th-century conflict
Context triple: [War of the League of Cognac, instanceOf, 16th-century conflict]
  • A. 13th-century conflict
    A 13th-century conflict is a military or political struggle that occurred between 1201 and 1300, shaped by medieval feudal structures, religious motivations, and emerging state powers.
  • B. early 18th-century conflict
    An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
  • C. 19th-century conflict
    A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
  • D. 15th-century event
    A 15th-century event is a historically significant occurrence that took place between 1401 and 1500, shaped by and contributing to the political, social, cultural, or technological transformations of that period.
  • E. 16th-century council
    A 16th-century council is a formal assembly of political, religious, or civic authorities convened during the 1500s to deliberate and decide on matters of governance, doctrine, law, or public policy.
  • 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_69aed95d315881908cbf1bf4a7215fbf completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:21 p.m.