Triple
T2507046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass in B minor |
E52608
|
entity |
| Predicate | containsMusicFrom |
P27310
|
FINISHED |
| Object | earlier cantata movements by Bach |
—
|
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: earlier cantata movements by Bach | Statement: [Mass in B minor, containsMusicFrom, earlier cantata movements by Bach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMusicFrom Context triple: [Mass in B minor, containsMusicFrom, earlier cantata movements by Bach]
-
A.
hasCommonMusic
Indicates that two entities share at least one piece of music preference, interest, or item in common.
-
B.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
C.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
D.
musicElement
chosen
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
E.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.