Triple
T38044131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 20 in G major, Op. 49 No. 2 |
E949568
|
entity |
| Predicate | sonataNumber |
P189901
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Piano Sonata No. 20 in G major, Op. 49 No. 2, sonataNumber, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sonataNumber Context triple: [Piano Sonata No. 20 in G major, Op. 49 No. 2, sonataNumber, 20]
-
A.
numberOfSonatas
Indicates the quantity of sonatas associated with a given entity.
-
B.
inBeethovenPianoSonataCycle
Indicates that something is part of, or occurs within, the cycle of Beethoven’s piano sonatas.
-
C.
movementCountFirstSonata
Indicates the number of movements contained in the first sonata.
-
D.
workNumberInSchubertCatalogue
Indicates that one entity specifies the identifying work number assigned to a composition within the Schubert catalogue for another entity.
-
E.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.