Triple
T38306005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in G minor, BWV 860 |
E1032345
|
entity |
| Predicate | relativeKey |
P142442
|
FINISHED |
| Object | B-flat major |
—
|
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 major | Statement: [Prelude in G minor, BWV 860, relativeKey, B-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeKey Context triple: [Prelude in G minor, BWV 860, relativeKey, B-flat major]
-
A.
relativeKeyOf
chosen
Indicates that one musical key stands in a relative relationship (sharing the same key signature but having a different tonic) to another key.
-
B.
keyRelation
Indicates a functional or defining association where one entity serves as a key or primary reference for accessing, identifying, or organizing another entity.
-
C.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
D.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
relativeAlias
Indicates that one entity is known or referred to by an alternative name or label that is contextually related to 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.