Triple
T28260331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata for Oboe and Piano |
E712564
|
entity |
| Predicate | hasMovementTitle |
P39539
|
FINISHED |
| Object | Élégie (second movement) |
—
|
NE NERFINISHED |
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: Élégie (second movement) | Statement: [Sonata for Oboe and Piano, hasMovementTitle, Élégie (second movement)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementTitle Context triple: [Sonata for Oboe and Piano, hasMovementTitle, Élégie (second movement)]
-
A.
movement1Title
chosen
Indicates the title or descriptive label assigned to a specific movement within a larger work or sequence.
-
B.
movement2Title
Indicates a relationship where a specific movement, action, or motion is associated with or labeled by a particular title or name.
-
C.
haveMovementFor
Indicates that an entity exhibits or is assigned a specific type or pattern of movement in relation to another entity or context.
-
D.
movement5Title
Indicates the title or label assigned to the fifth movement in a sequence of movements.
-
E.
titleHolderMovement
Indicates the transfer or change of which entity currently holds a particular title or position over time.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 11:11 p.m.