Triple
T28416946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 in F minor |
E719831
|
entity |
| Predicate | hasTempoMarkingSecondMovement |
P40272
|
FINISHED |
| Object | Larghetto |
—
|
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: Larghetto | Statement: [Piano Concerto No. 2 in F minor, hasTempoMarkingSecondMovement, Larghetto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempoMarkingSecondMovement Context triple: [Piano Concerto No. 2 in F minor, hasTempoMarkingSecondMovement, Larghetto]
-
A.
tempoMarkingSecondMovement
chosen
Indicates the tempo marking that applies specifically to the second movement of a musical work.
-
B.
timeSignatureSecondMovement
Indicates the time signature used in the second movement of a musical work.
-
C.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
D.
firstMovementTempoMarking
Indicates the tempo marking associated with the first movement of a work or composition.
-
E.
fourthMovementTempoMarking
Indicates the specified tempo marking used in the fourth movement of a musical work.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 1:31 a.m.