Triple
T37611538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regenlied Sonata |
E935795
|
entity |
| Predicate | workNumberWithinComposerViolinSonatas |
P188756
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Regenlied Sonata, workNumberWithinComposerViolinSonatas, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberWithinComposerViolinSonatas Context triple: [Regenlied Sonata, workNumberWithinComposerViolinSonatas, 1]
-
A.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
-
B.
workNumberInScriabinSonatas
Indicates the ordinal position or catalog number assigned to a work within the set of Scriabin’s piano sonatas.
-
C.
numberOfSonatas
Indicates the quantity of sonatas associated with a given entity.
-
D.
workNumberInBrahmsOeuvre
Indicates the catalog or opus number assigned to a specific work within Brahms’s complete body of compositions.
-
E.
workNumberInMozartSymphonies
Indicates the ordinal position or catalog number that a given work holds within the collection of Mozart’s symphonies.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:18 p.m.