Triple

T32034629
Position Surface form Disambiguated ID Type / Status
Subject Global Syriac Orthodox diaspora E818058 entity
Predicate instanceOf P0 FINISHED
Object Syriac Christian community C27572 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 community
Context triple: [Global Syriac Orthodox diaspora, instanceOf, Syriac Christian community]
  • A. Syriac Christian church
    A Syriac Christian church is a Christian community or building that follows the liturgical, theological, and cultural traditions of Syriac Christianity, often using the Syriac language in worship and rooted in the heritage of the ancient Near Eastern churches.
  • B. Syriac Christian chosen
    A Syriac Christian is a member of an Eastern Christian tradition that uses the Syriac language in its liturgy and theology, rooted in the ancient Aramaic-speaking communities of the Near East.
  • C. Syrian Christian
    A Syrian Christian is a member of a Christian community, primarily in the Middle East and South India, whose religious traditions and liturgy are historically rooted in Syriac language and Eastern Christian rites.
  • D. Melkite Christian
    A Melkite Christian is a member of an Eastern Catholic Church of the Byzantine tradition, historically rooted in the Middle East, that follows the Byzantine Rite while being in full communion with the Roman Catholic Church.
  • E. Arab Christians
    Arab Christians are members of Christian communities in the Arab world who share Arab cultural and linguistic heritage while practicing various Christian denominations such as Eastern Orthodox, Oriental Orthodox, Catholic, and Protestant 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_69f348fbc8148190b3c0f95d4772b153 completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:18 a.m.