Triple
T29772387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Methodist clergy |
E755283
|
entity |
| Predicate | hasSacramentalAuthority |
P125715
|
FINISHED |
| Object | baptism |
—
|
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: baptism | Statement: [United Methodist clergy, hasSacramentalAuthority, baptism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacramentalAuthority Context triple: [United Methodist clergy, hasSacramentalAuthority, baptism]
-
A.
confersSacrament
chosen
Indicates that one entity formally administers or bestows a religious sacrament upon another entity.
-
B.
hasFaithfulOfRite
Indicates that a religious body or authority has adherents who follow a specific liturgical rite.
-
C.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
D.
hasSacredInstitution
Indicates that an entity possesses, is associated with, or is the location of a recognized sacred or religious institution.
-
E.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 8:43 p.m.