Triple
T26105935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacraments of the Sick |
E658534
|
entity |
| Predicate | normativeMinister |
P159953
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [Sacraments of the Sick, normativeMinister, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativeMinister Context triple: [Sacraments of the Sick, normativeMinister, bishop]
-
A.
ministerIs
Indicates that one entity serves in the role or capacity of a minister in relation to another entity.
-
B.
hasMinister
Indicates that one entity serves as the minister (political, religious, or administrative official) responsible for or associated with another entity.
-
C.
typeOfMinister
Indicates the specific governmental or religious office or role that a particular minister holds.
-
D.
ministersIn
Indicates that one entity serves or carries out ministerial duties within the jurisdiction, organization, or domain of another entity.
-
E.
ministersIn
Indicates that a person serves in an official ministerial role within a specified government, organization, or jurisdiction.
- 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_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_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:58 p.m.