Triple
T31490417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridal Chorus |
E803389
|
entity |
| Predicate | lyricsOpeningWords |
P97549
|
FINISHED |
| Object | Treulich geführt ziehet dahin |
—
|
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: Treulich geführt ziehet dahin | Statement: [Bridal Chorus, lyricsOpeningWords, Treulich geführt ziehet dahin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricsOpeningWords Context triple: [Bridal Chorus, lyricsOpeningWords, Treulich geführt ziehet dahin]
-
A.
hasOpeningLyric
Indicates that one entity serves as the opening lyric of another entity, typically a song or musical work.
-
B.
introitOpeningWords
chosen
Indicates the relationship between a liturgical introit and the specific opening words with which it begins.
-
C.
lyricKeyword
Indicates that a lyric is associated with, or can be characterized by, a particular keyword or key phrase.
-
D.
openingVerseBy
Indicates that a work’s opening verse is authored, performed, or otherwise created by the specified entity.
-
E.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 9:38 p.m.