Triple
T35062252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 847 |
E1011622
|
entity |
| Predicate | hasTuningContext |
P119220
|
FINISHED |
| Object | well-tempered tuning systems |
—
|
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: well-tempered tuning systems | Statement: [BWV 847, hasTuningContext, well-tempered tuning systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTuningContext Context triple: [BWV 847, hasTuningContext, well-tempered tuning systems]
-
A.
usesTuningReference
Indicates that one entity adopts another entity as the pitch or frequency standard for tuning.
-
B.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
C.
hasTuneOrigin
Indicates that one entity’s tune or melody originates from, is derived from, or is based on another entity.
-
D.
isTunedTo
Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
-
E.
tuningType
chosen
Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired performance or behavior.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7860db9a881909ff887028b57acde |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.