Triple
T27305487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierbattista Pizzaballa |
E689042
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin Patriarch of Jerusalem |
C30223
|
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: Latin Patriarch of Jerusalem Context triple: [Pierbattista Pizzaballa, instanceOf, Latin Patriarch of Jerusalem]
-
A.
Melkite Greek Catholic patriarch
A Melkite Greek Catholic patriarch is the head bishop of the Melkite Greek Catholic Church, an Eastern Catholic Church in full communion with Rome that follows the Byzantine rite and leads its faithful in spiritual, liturgical, and administrative matters.
-
B.
Patriarch of Jerusalem
chosen
The Patriarch of Jerusalem is the senior ecclesiastical leader and bishop who holds spiritual authority and administrative responsibility over a Christian patriarchate based in Jerusalem.
-
C.
Syriac Orthodox Patriarch of Antioch
The Syriac Orthodox Patriarch of Antioch is the supreme spiritual leader and head of the Syriac Orthodox Church, traditionally regarded as the successor to the apostolic see of Antioch.
-
D.
Eastern Christian patriarch
An Eastern Christian patriarch is the highest-ranking bishop and spiritual leader of an autocephalous or autonomous Eastern Christian Church, holding authority over its doctrine, liturgy, and governance within a specific geographic or cultural sphere.
-
E.
Archbishop of Antioch
The Archbishop of Antioch is a senior ecclesiastical leader who serves as the chief bishop and spiritual head of a major Christian see historically centered in the ancient city of Antioch.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:24 a.m.