Triple
T17671515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ecclesiastical Hierarchy |
E440530
|
entity |
| Predicate | treatsSacrament |
P13034
|
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: [The Ecclesiastical Hierarchy, treatsSacrament, baptism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsSacrament Context triple: [The Ecclesiastical Hierarchy, treatsSacrament, baptism]
-
A.
celebratesSacrament
Indicates that an entity performs or participates in a formal religious sacramental rite involving another entity or occasion.
-
B.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
-
C.
includesSacrament
chosen
Indicates that one entity contains, involves, or incorporates a sacramental rite or practice as part of itself or its activities.
-
D.
practicesSacrament
Indicates that an entity performs or observes a specific religious sacrament as part of its ritual or faith practice.
-
E.
coreSacraments
Indicates that the specified religious rites are recognized as the fundamental or primary sacraments within a given religious tradition.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f68a038819084828ff73bcf1fcc |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:59 a.m.