Triple

T14914500
Position Surface form Disambiguated ID Type / Status
Subject Synod of Constantinople in 843 E371347 entity
Predicate instanceOf P0 FINISHED
Object event in Byzantine history 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: event in Byzantine history
Context triple: [Synod of Constantinople in 843, instanceOf, event in Byzantine history]
  • A. event in the Byzantine–Ottoman wars
    An "event in the Byzantine–Ottoman wars" is a specific historical occurrence—such as a battle, siege, treaty, or political development—that took place within the broader series of conflicts between the Byzantine Empire and the Ottoman state.
  • B. event in ancient history
    An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
  • 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. 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.
  • E. era of the Byzantine Empire
    The era of the Byzantine Empire encompasses the millennium-long continuation of the Eastern Roman Empire from the late antiquity reforms of Constantine the Great in the 4th century to the fall of Constantinople in 1453, marked by its Christian imperial culture, Greek language, and distinctive blend of Roman law, Orthodox theology, and Mediterranean trade.
  • 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_69d85cc7ea3481908228b5acb7d06f12 completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 2:27 a.m.