Triple
T215543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedictines |
E4812
|
entity |
| Predicate | spirituality |
P2154
|
FINISHED |
| Object | liturgical prayer |
—
|
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: liturgical prayer | Statement: [Benedictines, spirituality, liturgical prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spirituality Context triple: [Benedictines, spirituality, liturgical prayer]
-
A.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
religiousElement
chosen
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
viewOnSoul
Indicates a relationship where one entity holds or expresses a particular perspective, belief, or stance regarding the nature, existence, or characteristics of the soul.
-
D.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
-
E.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.