Triple
T32804966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ständchen |
E838996
|
entity |
| Predicate | LisztArrangementInstrumentation |
P40362
|
FINISHED |
| Object | solo piano |
—
|
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: solo piano | Statement: [Ständchen, LisztArrangementInstrumentation, solo piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LisztArrangementInstrumentation Context triple: [Ständchen, LisztArrangementInstrumentation, solo piano]
-
A.
musicalArrangement
Indicates that one entity is an arrangement or adaptation of another musical work.
-
B.
orchestralArrangement
Indicates that one musical work is arranged or adapted specifically for performance by an orchestra.
-
C.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
D.
hasPianoArrangement
chosen
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
E.
hasBrassArrangement
Indicates that something includes or is associated with a musical arrangement specifically written for brass instruments.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.