Triple
T28856127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 121 |
E728741
|
entity |
| Predicate | commonlySetToMusic |
P115911
|
FINISHED |
| Object | choral settings |
—
|
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: choral settings | Statement: [Psalm 121, commonlySetToMusic, choral settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlySetToMusic Context triple: [Psalm 121, commonlySetToMusic, choral settings]
-
A.
commonlySetToTune
chosen
Indicates that something is frequently assigned or adjusted to a particular tune or musical setting.
-
B.
setToMusicAs
Indicates that one entity (typically a text or work) has been adapted and arranged by another entity into a musical composition.
-
C.
setToMusicIn
Indicates that something (typically text or lyrics) has been arranged or adapted to be performed as music within a particular work or context.
-
D.
oftenTunesTo
Indicates that one entity frequently adjusts or sets its frequency, settings, or focus to match or receive another entity.
-
E.
hasCommonMusic
Indicates that two entities share at least one piece of music preference, interest, or item in common.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:45 a.m.