Triple
T32898096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 2 in A-flat major, Op. 39 |
E841529
|
entity |
| Predicate | hasExpressiveSlowMovement |
P83466
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Piano Sonata No. 2 in A-flat major, Op. 39, hasExpressiveSlowMovement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressiveSlowMovement Context triple: [Piano Sonata No. 2 in A-flat major, Op. 39, hasExpressiveSlowMovement, true]
-
A.
hasSlowMovement
chosen
Indicates that an entity exhibits movement that is slower than a normal or expected speed.
-
B.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
C.
slows
Indicates that one entity causes another entity’s speed, rate, or progress to decrease.
-
D.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
E.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:19 a.m.