Triple
T6772283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Benedictionibus |
E155071
|
entity |
| Predicate | isSacramentalBook |
P3101
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [De Benedictionibus, isSacramentalBook, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSacramentalBook Context triple: [De Benedictionibus, isSacramentalBook, true]
-
A.
hasLiturgicalBook
chosen
Indicates that one entity possesses, uses, or is associated with a specific liturgical book in a religious or worship context.
-
B.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
C.
coreSacraments
Indicates that the specified religious rites are recognized as the fundamental or primary sacraments within a given religious tradition.
-
D.
isClassifiedInRomanMissalAs
Indicates that something is assigned a specific category, designation, or status according to the classification system used in the Roman Missal.
-
E.
isMaterLectionis
Indicates that a letter functions as a mater lectionis, i.e., it represents a vowel sound rather than serving as a consonant.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24aaf948190a544cc28b7de67c4 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.