Triple
T12757077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in D major, BWV 850 |
E304886
|
entity |
| Predicate | hasCadence |
P106739
|
FINISHED |
| Object | authentic cadence in D major at the close |
—
|
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: authentic cadence in D major at the close | Statement: [Prelude in D major, BWV 850, hasCadence, authentic cadence in D major at the close]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadence Context triple: [Prelude in D major, BWV 850, hasCadence, authentic cadence in D major at the close]
-
A.
hasCadenza
Indicates that a musical work, passage, or performance includes or is associated with a cadenza section.
-
B.
hasCadenzaBy
Indicates that something (typically a musical work or passage) includes or is associated with a cadenza composed or authored by a specified entity.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
releaseCadence
Indicates how frequently and on what schedule something is released or made available.
-
E.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
- F. None of above. chosen
Provenance (4 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:27 p.m.