Triple
T36471325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordo Paenitentiae (Latin typical edition) |
E898545
|
entity |
| Predicate | concernedSacrament |
P23927
|
FINISHED |
| Object | Penance |
—
|
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: Penance | Statement: [Ordo Paenitentiae (Latin typical edition), concernedSacrament, Penance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernedSacrament Context triple: [Ordo Paenitentiae (Latin typical edition), concernedSacrament, Penance]
-
A.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
-
B.
associatedWithSacrament
chosen
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
-
C.
sacramentalUseOf
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
D.
confersSacrament
Indicates that one entity formally administers or bestows a religious sacrament upon another entity.
-
E.
celebratesSacrament
Indicates that an entity performs or participates in a formal religious sacramental rite involving another entity or occasion.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.