Triple
T23450578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonatas, Op. 50 |
E567767
|
entity |
| Predicate | movementCountInPart |
P32659
|
FINISHED |
| Object | multi-movement structure in each sonata |
—
|
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: multi-movement structure in each sonata | Statement: [Piano Sonatas, Op. 50, movementCountInPart, multi-movement structure in each sonata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementCountInPart Context triple: [Piano Sonatas, Op. 50, movementCountInPart, multi-movement structure in each sonata]
-
A.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
B.
movementCountPerQuartet
Indicates the number of individual movements contained within a single quartet.
-
C.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
D.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
E.
typicalMovementCountPerQuintet
Indicates the usual number of movements contained within a five-part (quintet) grouping.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64d3e9c8190a2596b067c4f5061 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.