Triple
T23871616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selig sind, die da Leid tragen |
E592742
|
entity |
| Predicate | movementOfComposer |
P153829
|
FINISHED |
| Object | Johannes Brahms |
—
|
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: Johannes Brahms | Statement: [Selig sind, die da Leid tragen, movementOfComposer, Johannes Brahms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementOfComposer Context triple: [Selig sind, die da Leid tragen, movementOfComposer, Johannes Brahms]
-
A.
associatedComposerMovement
Indicates a relationship linking a composer to a specific musical movement or stylistic period with which they are connected.
-
B.
movementInComposerOutput
chosen
Indicates a relationship where a specific musical movement is contained within, or forms part of, a particular composer's output or body of work.
-
C.
movementComposed
Indicates that a movement is formed by or consists of one or more component movements.
-
D.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
E.
favoriteComposer
Indicates that one entity is the preferred or most liked composer of another entity.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfe1f948190ad2c0d5bbe0c7240 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.