Triple
T12918027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in E-flat major, BWV 852 |
E309039
|
entity |
| Predicate | isWrittenFor |
P1996
|
FINISHED |
| Object | solo keyboard |
—
|
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: solo keyboard | Statement: [Prelude in E-flat major, BWV 852, isWrittenFor, solo keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenFor Context triple: [Prelude in E-flat major, BWV 852, isWrittenFor, solo keyboard]
-
A.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
originallyWrittenFor
chosen
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
D.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
E.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.