Triple

T16321260
Position Surface form Disambiguated ID Type / Status
Subject Arian controversy E396296 entity
Predicate instanceOf P0 FINISHED
Object 4th-century religious conflict C10888 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: 4th-century religious conflict
Context triple: [Arian controversy, instanceOf, 4th-century religious conflict]
  • A. 4th-century conflict chosen
    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. 6th-century conflict
    A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
  • C. 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.
  • D. 3rd-century event
    A 3rd-century event is any significant historical occurrence that took place between the years 201 and 300 CE, encompassing political, social, cultural, military, or religious developments of that period.
  • E. 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.
  • 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_69d87f255b788190a400eba031dd85d8 completed April 10, 2026, 4:40 a.m.
Created at: April 10, 2026, 5:06 a.m.