Triple
T4838722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Rosary |
E108126
|
entity |
| Predicate | spiritualBenefitsClaimed |
P46000
|
FINISHED |
| Object | growth in virtue |
—
|
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: growth in virtue | Statement: [Holy Rosary, spiritualBenefitsClaimed, growth in virtue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualBenefitsClaimed Context triple: [Holy Rosary, spiritualBenefitsClaimed, growth in virtue]
-
A.
spiritualRequirement
Indicates that one entity specifies or imposes a spiritual or religious condition that must be met by another entity.
-
B.
soteriologicalClaim
Indicates a relationship where an entity asserts or expresses a claim about salvation, redemption, or the means by which such spiritual deliverance is achieved.
-
C.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
D.
benefitsCause
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or cause.
-
E.
believedBenefit
chosen
Indicates that one entity considers or perceives another entity, action, or state as providing an advantage or positive outcome.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.