Triple
T229110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anointing of the Sick |
E4371
|
entity |
| Predicate | recipientCondition |
P379
|
FINISHED |
| Object | seriously ill |
—
|
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: seriously ill | Statement: [Anointing of the Sick, recipientCondition, seriously ill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recipientCondition Context triple: [Anointing of the Sick, recipientCondition, seriously ill]
-
A.
recipientsMayUse
Indicates that recipients are permitted to use something (e.g., content, data, or resources) under specified conditions.
-
B.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
C.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
D.
conditionForRecognition
Indicates that one entity specifies the requirement or circumstance under which another entity is acknowledged, accepted, or officially recognized.
-
E.
hasTypeOfRecipient
chosen
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.