Triple
T6909126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal call to holiness |
E159885
|
entity |
| Predicate | spiritualMeans |
P74075
|
FINISHED |
| Object | 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: prayer | Statement: [Universal call to holiness, spiritualMeans, prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualMeans Context triple: [Universal call to holiness, spiritualMeans, prayer]
-
A.
spiritualityType
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.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
D.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
E.
spiritualFruit
Indicates a relationship where a person exhibits or produces positive moral or spiritual qualities as an outcome of their inner spiritual life or influence.
- F. None of above. chosen
Provenance (4 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9be98748190b5cb698e66e3aa42 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.