Triple
T26105932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacraments of the Sick |
E658534
|
entity |
| Predicate | pastoralContext |
P96532
|
FINISHED |
| Object | hospice care |
—
|
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: hospice care | Statement: [Sacraments of the Sick, pastoralContext, hospice care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastoralContext Context triple: [Sacraments of the Sick, pastoralContext, hospice care]
-
A.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
-
B.
pastoralPurpose
chosen
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
-
C.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
D.
pastoralWorkLocation
Indicates the place where a person carries out their pastoral or ministerial duties.
-
E.
hasPastoralArea
Indicates that one entity is assigned to, responsible for, or associated with a specific pastoral area or pastoral care region 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607774de48190ba59eb5bfeaf3d5d |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:58 p.m.