Triple
T7290712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil of the Sick |
E164384
|
entity |
| Predicate | mayBeBlessedBy |
P20739
|
FINISHED |
| Object | priest in case of necessity |
—
|
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: priest in case of necessity | Statement: [Oil of the Sick, mayBeBlessedBy, priest in case of necessity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeBlessedBy Context triple: [Oil of the Sick, mayBeBlessedBy, priest in case of necessity]
-
A.
blessedBy
chosen
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
B.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
C.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
D.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
-
E.
firstBlessing
Indicates that an entity is the initial recipient or instance of a blessing in relation to another entity or context.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb6d4e308190af6b8c237988d7d8 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.