Triple

T11698627
Position Surface form Disambiguated ID Type / Status
Subject Hilarus of Rome E278061 entity
Predicate instanceOf P0 FINISHED
Object 5th-century Christian cleric C12379 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 Christian cleric
Context triple: [Hilarus of Rome, instanceOf, 5th-century Christian cleric]
  • A. 5th-century Italian bishop chosen
    A 5th-century Italian bishop was a high-ranking Christian cleric in Italy responsible for overseeing a diocese, guiding religious practice, and engaging in theological and political affairs during the late Roman and early post-Roman period.
  • B. 4th-century Christian bishop
    A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
  • C. 3rd-century Christian bishop
    A 3rd-century Christian bishop was a regional church leader responsible for overseeing Christian communities, doctrine, and worship during a period of persecution and theological development in the Roman Empire.
  • D. 6th-century Christian clergy
    6th-century Christian clergy were ordained religious leaders who administered sacraments, guided spiritual life, and often wielded significant social and political influence within the early medieval Christian Church.
  • E. Syriac Christian monk
    A Syriac Christian monk is a member of an ascetic religious community within the Syriac Christian tradition, devoted to prayer, contemplation, and communal or solitary monastic life shaped by Syriac liturgy, language, and theology.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 9:40 p.m.