Triple
T37202218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebster Jesu, hör mein Flehen |
E922068
|
entity |
| Predicate | likelyLiturgicalUse |
P9871
|
FINISHED |
| Object | Protestant worship |
—
|
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: Protestant worship | Statement: [Liebster Jesu, hör mein Flehen, likelyLiturgicalUse, Protestant worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyLiturgicalUse Context triple: [Liebster Jesu, hör mein Flehen, likelyLiturgicalUse, Protestant worship]
-
A.
aimsForLiturgicalUse
Indicates that something is intended or designed specifically for use in liturgical or formal religious worship contexts.
-
B.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
-
C.
usedInLiturgy
chosen
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
D.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
E.
liturgicalUsePromoted
Indicates that an entity actively encouraged or advocated for the adoption or increased practice of a particular liturgical use or rite.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.