Triple
T35290983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 851 |
E1019223
|
entity |
| Predicate | isContrapuntal |
P99482
|
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: [BWV 851, isContrapuntal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContrapuntal Context triple: [BWV 851, isContrapuntal, true]
-
A.
hasContrapuntalWriting
Indicates that one musical entity features contrapuntal writing in relation to another, meaning multiple independent melodic lines are combined according to contrapuntal principles.
-
B.
usesCounterpoint
chosen
Indicates that one entity employs counterpoint, combining independent melodic lines in a structured, interdependent musical relationship with another.
-
C.
contradictoryPairs
Indicates that the paired entities stand in direct logical opposition such that the truth of one necessarily implies the falsity of the other.
-
D.
tonalContrast
Indicates a relationship where two elements differ in their tonal qualities (such as lightness, darkness, or color value) to create visual distinction or emphasis.
-
E.
usesCantusFirmus
Indicates that one musical element is based on or incorporates a pre-existing cantus firmus melody as its structural foundation.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.