Triple
T33400070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hah |
E855271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syriac Orthodox Christian village |
C60092
|
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 Orthodox Christian village Context triple: [Hah, instanceOf, Syriac Orthodox Christian village]
-
A.
Assyrian Christian town
An Assyrian Christian town is a settlement predominantly inhabited by Assyrian Christians, characterized by their Syriac language, churches, and cultural traditions rooted in ancient Mesopotamian and early Christian heritage.
-
B.
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.
-
C.
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.
-
D.
Armenian Apostolic monastery
An Armenian Apostolic monastery is a religious complex where clergy of the Armenian Apostolic Church live, worship, and administer spiritual, educational, and cultural activities according to Armenian Christian tradition.
-
E.
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.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.