Triple
T27305508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierbattista Pizzaballa |
E689042
|
entity |
| Predicate | consecrationAsBishopBy |
P3357
|
FINISHED |
| Object | Leonardo Sandri |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Leonardo Sandri | Statement: [Pierbattista Pizzaballa, consecrationAsBishopBy, Leonardo Sandri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecrationAsBishopBy Context triple: [Pierbattista Pizzaballa, consecrationAsBishopBy, Leonardo Sandri]
-
A.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
B.
consecratedAsBishopDate
Indicates the date on which an individual was formally consecrated to the office of bishop.
-
C.
consecratedBishopOn
Indicates that one entity performed the act of consecrating another entity as a bishop on a specific date or occasion.
-
D.
consecratedBy
chosen
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
E.
appointedBishopBy
Indicates that one entity was formally made a bishop through the authority or decision of another entity.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:24 a.m.