Triple
T32787988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nachtstück No. 2 in C major, Op. 23 |
E838548
|
entity |
| Predicate | setComposer |
P175115
|
FINISHED |
| Object | Robert Schumann |
—
|
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: Robert Schumann | Statement: [Nachtstück No. 2 in C major, Op. 23, setComposer, Robert Schumann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setComposer Context triple: [Nachtstück No. 2 in C major, Op. 23, setComposer, Robert Schumann]
-
A.
dedicatedComposer
Indicates that one entity is a composer who is devoted or committed specifically to another entity or purpose.
-
B.
associatedComposerPosition
Indicates that there is a specific role, title, or position held by a composer in relation to a given context or entity.
-
C.
commissionedComposer
Indicates that one entity formally requested and funded another entity (a composer) to create a musical work.
-
D.
focusesOnComposer
Indicates that something (such as a work, study, or discussion) is primarily concerned with or centered around a particular composer.
-
E.
associatedComposerCatalog
Indicates a relationship between a work and a specific catalog of that composer’s works with which it is associated.
- F. None of above. chosen
Provenance (4 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:14 a.m.