Triple
T37611416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Sonatas, Op. 120 |
E935793
|
entity |
| Predicate | keyOfSecondWork |
P40856
|
FINISHED |
| Object | E-flat major |
—
|
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: E-flat major | Statement: [Clarinet Sonatas, Op. 120, keyOfSecondWork, E-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfSecondWork Context triple: [Clarinet Sonatas, Op. 120, keyOfSecondWork, E-flat major]
-
A.
keyWorkOf
Indicates that the subject is a central, defining, or most important work created by the object (such as an artist, author, or creator).
-
B.
secondWork
Indicates that one work is the second in order relative to another work within a sequence or set.
-
C.
keyOfWork
chosen
Indicates that one entity specifies the musical key in which a particular work is composed or performed.
-
D.
keyOfLastWork
Indicates the musical key in which an entity’s most recently created or performed work is set.
-
E.
keyWorkIn
Indicates that a key or primary work (such as a main publication, artwork, or creation) is associated with or produced within a particular context, collection, or entity.
- 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_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. |
Created at: May 3, 2026, 4:18 p.m.