Triple
T30898589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy... Hymns and Faith |
E787095
|
entity |
| Predicate | featuresSpiritualSongs |
P134858
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Legacy... Hymns and Faith, featuresSpiritualSongs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSpiritualSongs Context triple: [Legacy... Hymns and Faith, featuresSpiritualSongs, yes]
-
A.
devotionalMusic
chosen
Indicates a relationship where music is created, performed, or used as an expression of religious or spiritual devotion toward a deity, faith, or sacred context.
-
B.
hymnsDedicatedTo
Indicates that certain hymns are specifically devoted or addressed to a particular entity as their subject or object of veneration.
-
C.
devotionalPoets
Indicates a relationship in which poets are characterized by or associated with devotional (religious or spiritual) themes in their work.
-
D.
relatedChantOrSong
Indicates that one chant or song is associated with, derived from, or otherwise connected to another chant or song.
-
E.
featuresRichHarmonies
Indicates that the subject contains or employs complex, layered, and sonically dense harmonic structures.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: April 29, 2026, 8:50 p.m.