Triple
T23914763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Pieces for Orchestra, Op. 10 |
E602050
|
entity |
| Predicate | movementList |
P59821
|
FINISHED |
| Object | I. Sehr ruhig und zart |
—
|
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: I. Sehr ruhig und zart | Statement: [Five Pieces for Orchestra, Op. 10, movementList, I. Sehr ruhig und zart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementList Context triple: [Five Pieces for Orchestra, Op. 10, movementList, I. Sehr ruhig und zart]
-
A.
movementName
chosen
Indicates the specific title or designation assigned to a particular movement or action.
-
B.
movementForm
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
C.
movementRepresentedBy
Indicates that a movement or motion of an entity is depicted, encoded, or symbolized by another entity (such as a sign, pattern, or representation).
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
moves
Indicates that an entity changes its position or location over time, typically from one place to another.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce97f694819087215ed9f18b290e |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:39 p.m.