Triple
T1428035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Rites |
E30378
|
entity |
| Predicate | mayBeGivenTo |
P28411
|
FINISHED |
| Object | unconscious person presumed to desire the sacraments |
—
|
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: unconscious person presumed to desire the sacraments | Statement: [Last Rites, mayBeGivenTo, unconscious person presumed to desire the sacraments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeGivenTo Context triple: [Last Rites, mayBeGivenTo, unconscious person presumed to desire the sacraments]
-
A.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
B.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
C.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
D.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
E.
canServeIn
Indicates that one entity is eligible, authorized, or suitable to perform a role, function, or duty within another entity, context, or organization.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.