Triple
T22523023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasrani Mappila |
E556827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | St. Thomas Christian community |
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: St. Thomas Christian community Context triple: [Nasrani Mappila, instanceOf, St. Thomas Christian community]
-
A.
Syrian Christian
chosen
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.
-
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.
Syro-Malankara Catholic eparchy
A Syro-Malankara Catholic eparchy is a territorial jurisdiction of the Syro-Malankara Catholic Church, headed by a bishop, responsible for the pastoral care, administration, and liturgical life of the faithful within its defined region.
-
D.
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.
-
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.
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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.