Triple
T31434110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allein Gott in der Höh sei Ehr |
E801876
|
entity |
| Predicate | usedAsCantusFirmusIn |
P183726
|
FINISHED |
| Object | St. Paul, Op. 36 |
—
|
NE NERFINISHED |
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: St. Paul, Op. 36 | Statement: [Allein Gott in der Höh sei Ehr, usedAsCantusFirmusIn, St. Paul, Op. 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCantusFirmusIn Context triple: [Allein Gott in der Höh sei Ehr, usedAsCantusFirmusIn, St. Paul, Op. 36]
-
A.
usesCantusFirmus
Indicates that one musical element is based on or incorporates a pre-existing cantus firmus melody as its structural foundation.
-
B.
hasPlainchantCantusFirmus
chosen
Indicates that something (typically a musical work or section) uses a plainchant melody as its cantus firmus foundation.
-
C.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
D.
notableChorale
Indicates that a subject is recognized for or associated with a significant or distinguished chorale work or composition.
-
E.
usesLiturgicalMelody
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 30, 2026, 9 p.m.