Triple
T8602470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 3 in F minor, Op. 14 |
E203711
|
entity |
| Predicate | middleMovementBasedOn |
P83809
|
FINISHED |
| Object | theme by Clara Wieck |
—
|
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: theme by Clara Wieck | Statement: [Piano Sonata No. 3 in F minor, Op. 14, middleMovementBasedOn, theme by Clara Wieck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: middleMovementBasedOn Context triple: [Piano Sonata No. 3 in F minor, Op. 14, middleMovementBasedOn, theme by Clara Wieck]
-
A.
basedOnMovement
Indicates that something is determined, derived, or decided according to the movement or motion of an entity.
-
B.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
C.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
D.
movementCenter
Indicates the central point or primary location around which an entity’s movement or motion is organized or focused.
-
E.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
- F. None of above. chosen
Provenance (4 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46da609881909a6d851915e8df14 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:24 p.m.