Triple
T11775970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Rondo: Allegro in E-flat major |
E280018
|
entity |
| Predicate | hasPrecedingMovement |
P25144
|
FINISHED |
| Object | II. Adagio un poco mosso |
—
|
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: II. Adagio un poco mosso | Statement: [III. Rondo: Allegro in E-flat major, hasPrecedingMovement, II. Adagio un poco mosso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrecedingMovement Context triple: [III. Rondo: Allegro in E-flat major, hasPrecedingMovement, II. Adagio un poco mosso]
-
A.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
B.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
C.
hasImportantMovement
Indicates that an entity is associated with a movement (e.g., social, artistic, political) that is considered significant or influential.
-
D.
hasSubmovement
Indicates that a movement or action is composed of, or contains within it, a smaller constituent movement.
-
E.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.