Triple
T20789627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beth Qatraye |
E511736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syriac Christian cultural region |
C44088
|
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 cultural region Context triple: [Beth Qatraye, instanceOf, Syriac Christian cultural region]
-
A.
center of Syriac Christianity
The center of Syriac Christianity is the spiritual, cultural, and often administrative hub from which Syriac Christian liturgy, theology, scholarship, and communal life radiate and are preserved.
-
B.
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.
-
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.
Christian community in Asia Minor
A Christian community in Asia Minor is a group of believers in Jesus Christ living in the Roman provinces of western Anatolia, sharing a common faith, worship, and communal life shaped by early Christian teachings and local cultural contexts.
-
E.
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.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:38 p.m.