Triple
T29207044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 3 in F minor, Op. 5 |
E740438
|
entity |
| Predicate | hasIntermezzoMovement |
P46147
|
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. 3 in F minor, Op. 5, hasIntermezzoMovement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntermezzoMovement Context triple: [Piano Sonata No. 3 in F minor, Op. 5, hasIntermezzoMovement, true]
-
A.
containsInterludes
chosen
Indicates that one entity (typically a work or composition) includes one or more interludes within its structure.
-
B.
hasAndanteMovement
Indicates that a musical work includes a movement marked at an andante (moderately slow, walking) tempo.
-
C.
hasScherzoMovement
Indicates that a musical work includes a scherzo as one of its movements.
-
D.
hasExtendedInstrumentalSections
Indicates that a musical work contains notably long instrumental passages beyond typical song structure.
-
E.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 28, 2026, 12:09 p.m.