Triple
T11475079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C major (BWV 1005) |
E272005
|
entity |
| Predicate | performancePracticeContext |
P99493
|
FINISHED |
| Object | unaccompanied violin |
—
|
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: unaccompanied violin | Statement: [C major (BWV 1005), performancePracticeContext, unaccompanied violin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performancePracticeContext Context triple: [C major (BWV 1005), performancePracticeContext, unaccompanied violin]
-
A.
musicPractice
Indicates engaging in the activity of practicing or rehearsing music, typically to improve skill or prepare for performance.
-
B.
physicalPracticeComponent
Indicates that something is a physical or bodily activity that forms part of a larger practice or routine.
-
C.
performedInContextOf
Indicates that an action or event was carried out within, and is meaningfully related to, a specific situational, procedural, or environmental context.
-
D.
firstPerformanceContext
Indicates the situational or environmental context in which an entity’s first performance or debut took place.
-
E.
performanceArea
Indicates the area or space in which a performance, show, or event takes place.
- F. None of above. chosen
Provenance (4 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:36 p.m.