Triple
T37611806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanze in F major, Op. 118 No. 5 |
E935802
|
entity |
| Predicate | movementNumberWithinCollection |
P12040
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Romanze in F major, Op. 118 No. 5, movementNumberWithinCollection, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberWithinCollection Context triple: [Romanze in F major, Op. 118 No. 5, movementNumberWithinCollection, 5]
-
A.
movementNumber
chosen
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
B.
collectionPosition
Indicates the relative ordering or placement of an item within a collection or sequence.
-
C.
collectorNumber
Indicates the identifying number assigned to a specific item within a collection, typically reflecting its order or position in that collection.
-
D.
movementNumberInOp130
Indicates the specific movement number of a work within Opus 130.
-
E.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.