Triple
T11631343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Sonata No. 2 in A minor, BWV 1003 |
E276404
|
entity |
| Predicate | finalMovement |
P83468
|
FINISHED |
| Object | Allegro |
—
|
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: Allegro | Statement: [Violin Sonata No. 2 in A minor, BWV 1003, finalMovement, Allegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMovement Context triple: [Violin Sonata No. 2 in A minor, BWV 1003, finalMovement, Allegro]
-
A.
finalMovementKey
Indicates that one movement in a sequence is designated as the last or concluding movement, often used as a key or reference to the final step in a process or animation.
-
B.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
C.
hasFinaleMovement
chosen
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
E.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.