Triple
T12710902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zita of Bourbon-Parma |
E303712
|
entity |
| Predicate | causeForBeatificationOpened |
P106300
|
FINISHED |
| Object | 2009 |
—
|
LITERAL FINISHED |
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: 2009 | Statement: [Zita of Bourbon-Parma, causeForBeatificationOpened, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeForBeatificationOpened Context triple: [Zita of Bourbon-Parma, causeForBeatificationOpened, 2009]
-
A.
yearCauseForCanonizationOpened
Indicates the year in which the formal process or cause for an entity’s canonization was officially opened.
-
B.
reasonForCanonization
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
C.
beatificationDate
Indicates the date on which a person was officially declared blessed (beatified) in a religious context.
-
D.
causeForCanonizationOpenedBy
Indicates that an entity is the person or authority who formally initiated the cause for another entity’s canonization.
-
E.
placeOfBeatification
Indicates the location where a person was formally declared beatified in a religious context.
- F. None of above. chosen
Provenance (4 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96207b2d881908314efc3e350aa78 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:23 p.m.