Triple

T32953244
Position Surface form Disambiguated ID Type / Status
Subject Jacob of Edessa E843019 entity
Predicate instanceOf P0 FINISHED
Object Syriac Christian scholar C8652 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: Syriac Christian scholar
Context triple: [Jacob of Edessa, instanceOf, Syriac Christian scholar]
  • A. Syriac Christian theologian chosen
    A Syriac Christian theologian is a scholar or religious thinker who develops, interprets, and systematizes Christian doctrine within the Syriac linguistic, liturgical, and cultural tradition.
  • B. Syriac Christian bishop
    A Syriac Christian bishop is a high-ranking cleric within the Syriac Christian traditions who oversees dioceses, administers sacraments, preserves Syriac liturgical and theological heritage, and provides spiritual and administrative leadership to clergy and laity.
  • C. 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.
  • D. Syriac Christian poet
    A Syriac Christian poet is a writer who composes religious and often liturgical verse in the Syriac language, blending biblical themes, theology, and local cultural motifs within the Syriac Christian tradition.
  • E. Alexandrian theologian
    An Alexandrian theologian is a Christian thinker associated with the theological tradition of Alexandria, known for its allegorical interpretation of Scripture, engagement with Greek philosophy, and influential contributions to early Christian doctrine.
  • 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_69f3494a31f481909057136e49b4fe60 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:21 a.m.