Triple
T35062231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 847 |
E1011622
|
entity |
| Predicate | subjectInterval |
P194386
|
FINISHED |
| Object | stepwise motion with repeated notes |
—
|
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: stepwise motion with repeated notes | Statement: [BWV 847, subjectInterval, stepwise motion with repeated notes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectInterval Context triple: [BWV 847, subjectInterval, stepwise motion with repeated notes]
-
A.
usesInterval
Indicates that one entity operates, functions, or is defined within a specific time or value interval associated with another entity.
-
B.
appointmentFrequency
Indicates how often appointments are scheduled or expected to occur within a given time period.
-
C.
recommendedUsageInterval
Indicates the time interval at which something is advised or intended to be used, applied, or performed.
-
D.
intervalAct
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between entities.
-
E.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:01 p.m.