Triple
T23581369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata No. 12 in G major, Op. 2 |
E582212
|
entity |
| Predicate | hasBassoContinuo |
P147456
|
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: [Sonata No. 12 in G major, Op. 2, hasBassoContinuo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBassoContinuo Context triple: [Sonata No. 12 in G major, Op. 2, hasBassoContinuo, true]
-
A.
usesBassoContinuo
chosen
Indicates that an entity employs or incorporates basso continuo as part of its musical texture or accompaniment.
-
B.
hasNotableBassline
Indicates that something (typically a piece of music) features a bassline that is particularly prominent, distinctive, or otherwise noteworthy.
-
C.
hasBassist
Indicates that an entity (typically a musical group or band) has another entity serving in the role of its bassist.
-
D.
hasBassIntroBy
Indicates a relationship where a musical piece features an introductory section performed or led by a bass instrument or bass player.
-
E.
hasMelodyInstrument
Indicates that something uses or features a particular instrument to carry the main melody.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02c265c819094728220d77172c6 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.