Triple
T12161941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartets, Op. 76 |
E289728
|
entity |
| Predicate | keyOfContainedWork |
P40856
|
FINISHED |
| Object | Op. 76 No. 1 in G 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: Op. 76 No. 1 in G major | Statement: [String Quartets, Op. 76, keyOfContainedWork, Op. 76 No. 1 in G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfContainedWork Context triple: [String Quartets, Op. 76, keyOfContainedWork, Op. 76 No. 1 in G 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.
nicknameOfContainedWork
Indicates that a name is a nickname or informal title used for a work that is contained within another larger work.
-
C.
keyOfWork
chosen
Indicates that one entity specifies the musical key in which a particular work is composed or performed.
-
D.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
E.
keyOfLastWork
Indicates the musical key in which an entity’s most recently created or performed work is set.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.