Triple
T16856250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto |
E409791
|
entity |
| Predicate | commonSecondMovementCharacter |
P84751
|
FINISHED |
| Object | slow 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: slow movement | Statement: [Piano Concerto, commonSecondMovementCharacter, slow movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSecondMovementCharacter Context triple: [Piano Concerto, commonSecondMovementCharacter, slow movement]
-
A.
secondMovementCharacter
chosen
Indicates the characteristic or quality that defines the second movement of a multi-movement work.
-
B.
secondMovementKey
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
C.
secondMovementTitle
Indicates the title or name given to the second movement of a multi-movement musical work.
-
D.
secondMovementForm
Indicates that an entity is in the form or structure of the second movement within a larger multi-movement work or sequence.
-
E.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37d69a08190af18b421066f44f1 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.