Triple
T10039470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 in C minor "Resurrection" |
E205256
|
entity |
| Predicate | vocalEntryMovement |
P33166
|
FINISHED |
| Object | fourth movement |
—
|
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: fourth movement | Statement: [Symphony No. 2 in C minor "Resurrection", vocalEntryMovement, fourth movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalEntryMovement Context triple: [Symphony No. 2 in C minor "Resurrection", vocalEntryMovement, fourth movement]
-
A.
hasVocalPartInMovement
chosen
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
B.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
C.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
-
D.
vocalArrangement
Indicates the specific way vocal parts or voices are organized, structured, and combined within a musical work or performance.
-
E.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee186708190bc9fecd637b4f7e6 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.