Triple
T12968987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodoret of Cyrrhus |
E321343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syrian Christian |
C32262
|
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: Syrian Christian Context triple: [Theodoret of Cyrrhus, instanceOf, Syrian Christian]
-
A.
Syriac Christian
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Egyptian Christian
An Egyptian Christian is a person from Egypt who follows the Christian faith, often belonging to historic communities such as the Coptic Orthodox Church, and whose religious identity is intertwined with Egypt’s ancient and modern cultural heritage.
- F. None of above. chosen
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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:33 p.m.