Triple
T19615721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Caprices for Solo Violin, Op. 1 |
E470853
|
entity |
| Predicate | keyOfNo22 |
P83481
|
FINISHED |
| Object | F 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: F major | Statement: [24 Caprices for Solo Violin, Op. 1, keyOfNo22, F major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfNo22 Context triple: [24 Caprices for Solo Violin, Op. 1, keyOfNo22, F major]
-
A.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
B.
keyOfSuite2
Indicates that something serves as the key (access or identifier) specifically for a second suite or the second instance of a suite.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyOfPiece2
chosen
Indicates that an entity serves as the musical key associated with a second piece or version of a composition.
-
E.
keyVow
Indicates a formal promise or commitment that is central or essential to an agreement, relationship, or situation.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cf418081909d69d5bd9c479fed |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.