Triple
T4578537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C.Ss.R. |
E101797
|
entity |
| Predicate | orderSpirituality |
P49306
|
FINISHED |
| Object | Alphonsian spirituality |
—
|
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: Alphonsian spirituality | Statement: [C.Ss.R., orderSpirituality, Alphonsian spirituality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderSpirituality Context triple: [C.Ss.R., orderSpirituality, Alphonsian spirituality]
-
A.
spiritualityType
chosen
Indicates the specific kind or category of spirituality associated with an entity.
-
B.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
-
C.
religiousMood
Indicates a prevailing emotional or spiritual atmosphere associated with religious experience, practice, or devotion between entities.
-
D.
inTheSpiritOf
Indicates that one entity acts, is created, or is characterized in a manner that follows the style, principles, or intent exemplified by another entity.
-
E.
religiousNature
Indicates that something possesses a religious character, quality, or orientation, such as being related to faith, worship, doctrine, or spiritual practice.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.