Triple
T36219481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 867 |
E1047803
|
entity |
| Predicate | hasPreludeKey |
P192403
|
FINISHED |
| Object | B-flat minor |
—
|
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: B-flat minor | Statement: [BWV 867, hasPreludeKey, B-flat minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreludeKey Context triple: [BWV 867, hasPreludeKey, B-flat minor]
-
A.
hasKeyOfPrelude
chosen
Indicates that one entity possesses or is associated with the musical key in which the prelude of another entity (such as a musical work or movement) is written.
-
B.
hasPrelude
Indicates that one entity includes or is associated with a preceding introductory section or preface to another entity.
-
C.
hasPreambleContext
Indicates that something is associated with or occurs within the contextual setting provided by a preamble (such as introductory or prefatory material).
-
D.
hasPreambleReferencing
Indicates that one document’s preamble explicitly refers to or cites another entity, such as a law, document, or provision.
-
E.
hasKeyPrediction
Indicates that one entity contains or provides a primary or most important predicted value or outcome for another entity.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.