Triple
T12012295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 in B-flat major, Op. 60 |
E285930
|
entity |
| Predicate | fourthMovementCharacter |
P83473
|
FINISHED |
| Object | fast finale |
—
|
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: fast finale | Statement: [Symphony No. 4 in B-flat major, Op. 60, fourthMovementCharacter, fast finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthMovementCharacter Context triple: [Symphony No. 4 in B-flat major, Op. 60, fourthMovementCharacter, fast finale]
-
A.
fourthMovementType
chosen
Indicates the type or character of the fourth movement in a multi-movement work or sequence.
-
B.
fourthMovementKey
Indicates the musical key in which the fourth movement of a multi-movement work is composed or performed.
-
C.
fourthMovementTitle
Indicates the title or name given to the fourth movement of a multi-movement musical work.
-
D.
secondMovementCharacter
Indicates the characteristic or quality that defines the second movement of a multi-movement work.
-
E.
fourthMovementForm
Indicates that one entity is the formal structure or type of the fourth movement within a larger multi-movement work associated with another entity.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.