Triple

T10347651
Position Surface form Disambiguated ID Type / Status
Subject Council of Rimini E243792 entity
Predicate instanceOf P0 FINISHED
Object 4th-century religious event C1474 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 event
Context triple: [Council of Rimini, instanceOf, 4th-century religious event]
  • A. 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.
  • B. 5th-century event
    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.
  • C. event in church history chosen
    An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
  • D. 16th-century religious event
    A 16th-century religious event is a historically situated occurrence, such as a council, reform, conflict, or ritual, that reflects and influences the era’s intense transformations in faith, doctrine, and church authority.
  • E. 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.
  • 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_69d381b22b8c8190aaed476be5f872a9 completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 11:56 a.m.