Triple
T8520177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 in D minor, Op. 120 |
E201674
|
entity |
| Predicate | typicalFormOfFirstMovement |
P83104
|
FINISHED |
| Object | sonata form (modified) |
—
|
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: sonata form (modified) | Statement: [Symphony No. 4 in D minor, Op. 120, typicalFormOfFirstMovement, sonata form (modified)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFormOfFirstMovement Context triple: [Symphony No. 4 in D minor, Op. 120, typicalFormOfFirstMovement, sonata form (modified)]
-
A.
tonalityOfFirstMovement
Indicates the key or tonal center in which the first movement of a musical work is composed.
-
B.
firstMovementTitle
Indicates the title or name given to the first movement of a multi-movement work.
-
C.
firstMovementKey
Indicates the musical key in which the first movement of a multi-movement work is composed.
-
D.
typicalMovementCountPerConcerto
Indicates the usual or standard number of movements that a concerto typically contains.
-
E.
tonalityOfSecondMovement
Indicates the key or tonal center that characterizes the second movement of a musical work.
- F. None of above. chosen
Provenance (4 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.