Triple
T12895490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in D minor, BWV 851 |
E308480
|
entity |
| Predicate | hasOpusStructure |
P841
|
FINISHED |
| Object | paired prelude and fugue |
—
|
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: paired prelude and fugue | Statement: [Fugue in D minor, BWV 851, hasOpusStructure, paired prelude and fugue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusStructure Context triple: [Fugue in D minor, BWV 851, hasOpusStructure, paired prelude and fugue]
-
A.
hasOpusForm
Indicates that an entity (such as a work or composition) is associated with a specific opus form or cataloging format.
-
B.
hasOpusGroup
Indicates that a work or composition belongs to, or is categorized within, a particular opus grouping or collection.
-
C.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
D.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
E.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.