Triple
T8468783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasiestücke, Op. 12 |
E200229
|
entity |
| Predicate | movementNumberOf |
P12040
|
FINISHED |
| Object | 1: Des Abends |
—
|
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: 1: Des Abends | Statement: [Fantasiestücke, Op. 12, movementNumberOf, 1: Des Abends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberOf Context triple: [Fantasiestücke, Op. 12, movementNumberOf, 1: Des Abends]
-
A.
movementNumber
chosen
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
B.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
C.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d445f48190884df64bb1aebd41 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.