Triple
T33450028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nativity of Our Lord Parish |
E856609
|
entity |
| Predicate | hasSacramentalLife |
P55456
|
FINISHED |
| Object | Baptism |
—
|
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: Baptism | Statement: [Nativity of Our Lord Parish, hasSacramentalLife, Baptism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacramentalLife Context triple: [Nativity of Our Lord Parish, hasSacramentalLife, Baptism]
-
A.
hasLiturgicalLife
Indicates that an entity participates in or maintains practices, rituals, and rhythms associated with liturgical worship.
-
B.
sharesSacramentalLife
Indicates that two entities participate together in the same sacramental practices or rites, sharing a common sacramental life.
-
C.
hasParishLife
Indicates that an entity maintains or supports organized parish-based religious and community life activities.
-
D.
hasCommunion
Indicates that one entity shares or participates in a close, often spiritual or sacramental, union or fellowship with another entity.
-
E.
coreSacraments
chosen
Indicates that the specified religious rites are recognized as the fundamental or primary sacraments within a given religious tradition.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.