Triple
T33898098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Zayd Hunayn ibn Ishaq al-Ibadi |
E868970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arab Christian |
C28497
|
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: Arab Christian Context triple: [Abu Zayd Hunayn ibn Ishaq al-Ibadi, instanceOf, Arab Christian]
-
A.
Arab Christians
chosen
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.
-
B.
Palestinian Christian
A Palestinian Christian is a person of Palestinian heritage who practices Christianity and belongs to the indigenous Christian communities of historic Palestine.
-
C.
Maronite Christian
A Maronite Christian is a member of an Eastern Catholic Church of the West Syriac tradition, in full communion with Rome, whose faith and identity are historically rooted in the teachings of Saint Maron and centered largely in Lebanon and its diaspora.
-
D.
Lebanese Maronite
A Lebanese Maronite is a member of the Maronite Catholic community originating from Lebanon, characterized by its Syriac Christian liturgical tradition, communion with the Roman Catholic Church, and significant cultural and historical influence in Lebanese society.
-
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.
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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.