Triple

T11990417
Position Surface form Disambiguated ID Type / Status
Subject Eutychian (Monophysite) controversy E285389 entity
Predicate instanceOf P0 FINISHED
Object 5th-century religious controversy 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: 5th-century religious controversy
Context triple: [Eutychian (Monophysite) controversy, instanceOf, 5th-century religious controversy]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. religious controversy
    Religious controversy is a sustained conflict or debate arising from differing beliefs, doctrines, practices, or interpretations within or between religious traditions.
  • 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:46 p.m.