Triple
T8729285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 in D minor |
E207211
|
entity |
| Predicate | vocalMovement |
P33166
|
FINISHED |
| Object | IV: alto solo with orchestra |
—
|
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: IV: alto solo with orchestra | Statement: [Symphony No. 3 in D minor, vocalMovement, IV: alto solo with orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalMovement Context triple: [Symphony No. 3 in D minor, vocalMovement, IV: alto solo with orchestra]
-
A.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
-
B.
hasVocalPartInMovement
chosen
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
C.
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.
-
D.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
E.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d19fdc88190860e0c9c93ab79ce |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.