Triple
T8178912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England clergy |
E191008
|
entity |
| Predicate | ordinationRite |
P81280
|
FINISHED |
| Object | laying on of hands |
—
|
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: laying on of hands | Statement: [Church of England clergy, ordinationRite, laying on of hands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinationRite Context triple: [Church of England clergy, ordinationRite, laying on of hands]
-
A.
ordains
Indicates that one entity formally appoints or invests another with authority, office, or a religious role through an official or ceremonial act.
-
B.
liturgicalSequence
Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
-
C.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
D.
dominantRite
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
-
E.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4abd9768819091298e4dd995ac96 |
completed | March 31, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:40 p.m.