Triple
T34682090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salesian Youth Movement |
E890647
|
entity |
| Predicate | hasSpiritualityCharacteristic |
P63846
|
FINISHED |
| Object | joy |
—
|
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: joy | Statement: [Salesian Youth Movement, hasSpiritualityCharacteristic, joy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualityCharacteristic Context triple: [Salesian Youth Movement, hasSpiritualityCharacteristic, joy]
-
A.
spiritualityCharacteristic
chosen
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
B.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
C.
hasSpiritualLife
Indicates that an entity possesses or engages in a spiritual or religious inner life, practice, or orientation.
-
D.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
E.
hasSpiritualPresence
Indicates that an entity possesses, embodies, or exerts a non-physical, spiritual influence or presence in relation to another 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 1, 2026, 2:05 a.m.