Triple
T12012369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven string quartets |
E285932
|
entity |
| Predicate | lateQuartetsOpus |
P40276
|
FINISHED |
| Object | Op. 127 |
—
|
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. 127 | Statement: [Beethoven string quartets, lateQuartetsOpus, Op. 127]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lateQuartetsOpus Context triple: [Beethoven string quartets, lateQuartetsOpus, Op. 127]
-
A.
workNumberWithinLateQuartets
chosen
Indicates that a work’s identifying number falls within the subset of compositions known as the “late quartets.”
-
B.
keyOfEighthConcerto
Indicates the musical key in which the eighth concerto of a given composer or cataloged series is written.
-
C.
keyOfFifthConcerto
Indicates the musical key in which the fifth concerto of a given composer or cataloged set is written.
-
D.
keyOfTwelfthConcerto
Indicates that one entity specifies the musical key in which the twelfth concerto of another entity is composed.
-
E.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.