Triple

T9956144
Position Surface form Disambiguated ID Type / Status
Subject War between Odoacer and Theodoric E195450 entity
Predicate instanceOf P0 FINISHED
Object late 5th-century conflict C1434 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: late 5th-century conflict
Context triple: [War between Odoacer and Theodoric, instanceOf, late 5th-century conflict]
  • A. 4th-century conflict
    A 4th-century conflict is a historical dispute, war, or series of hostilities that occurred between 300 and 399 CE, shaped by the political, religious, and social dynamics of late antiquity.
  • B. 7th-century conflict
    A 7th-century conflict is a military or political struggle that occurred between 600 and 699 CE, typically involving early medieval states, empires, or tribes and shaped by the religious, cultural, and territorial dynamics of that era.
  • C. 5th-century event chosen
    A 5th-century event is a historically significant occurrence that took place between the years 401 and 500 CE, shaping the political, social, cultural, or religious landscape of its time.
  • D. 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.
  • E. 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.
  • 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_69ca82eaaa008190a54fa1a9f954b9ad completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 8:46 p.m.