Triple
T36912260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aria in G major |
E912940
|
entity |
| Predicate | workNumberWithinBWV |
P97961
|
FINISHED |
| Object | 988 |
—
|
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: 988 | Statement: [Aria in G major, workNumberWithinBWV, 988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberWithinBWV Context triple: [Aria in G major, workNumberWithinBWV, 988]
-
A.
workNumberInBWV
chosen
Indicates that a musical work is identified by a specific catalog number within the Bach-Werke-Verzeichnis (BWV) catalog.
-
B.
BWVNumber
Indicates the catalog number assigned to a musical work in the Bach-Werke-Verzeichnis (BWV) system, specifying its place in the catalog of J.S. Bach’s compositions.
-
C.
workNumberWithinCantata
Indicates that a musical work’s number is specified within the ordered sequence of pieces that make up a cantata.
-
D.
BWVNumberRange
Indicates that a work is identified as belonging to a specified range of Bach-Werke-Verzeichnis (BWV) catalogue numbers.
-
E.
workNumberInBrahmsOeuvre
Indicates the catalog or opus number assigned to a specific work within Brahms’s complete body of compositions.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdb0e0b881908890f7e8aae30f5d |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.