Triple
T25682622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novena to Our Lady of Lourdes |
E643980
|
entity |
| Predicate | oftenPrayedBy |
P162109
|
FINISHED |
| Object | individual Catholics |
—
|
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: individual Catholics | Statement: [Novena to Our Lady of Lourdes, oftenPrayedBy, individual Catholics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenPrayedBy Context triple: [Novena to Our Lady of Lourdes, oftenPrayedBy, individual Catholics]
-
A.
praysIn
Indicates that an entity performs the act of praying within or at a particular place or setting.
-
B.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
-
C.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
D.
praysFor
Indicates that one entity directs prayers or spiritual petitions on behalf of another entity.
-
E.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 8:03 p.m.