Triple
T32804971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ständchen |
E838996
|
entity |
| Predicate | hasAccompanimentFigure |
P92070
|
FINISHED |
| Object | broken chords in 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: broken chords in piano | Statement: [Ständchen, hasAccompanimentFigure, broken chords in piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccompanimentFigure Context triple: [Ständchen, hasAccompanimentFigure, broken chords in piano]
-
A.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
B.
requiresAccompaniment
Indicates that one entity must be accompanied or attended by another entity in order for an action, event, or condition to occur or be valid.
-
C.
accompanimentType
chosen
Indicates the specific manner or style in which one entity accompanies or supports another (e.g., musically, contextually, or functionally).
-
D.
mayBeAccompaniedBy
Indicates that one entity can optionally be present together with or alongside another entity.
-
E.
hasPianoAccompaniment
Indicates that something (such as a musical work or performance) is accompanied by a piano part.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:15 a.m.