Triple
T22196600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in E minor, Op. 4 No. 2, RV 279 |
E548564
|
entity |
| Predicate | keyFamily |
P57753
|
FINISHED |
| Object | minor mode |
—
|
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: minor mode | Statement: [Violin Concerto in E minor, Op. 4 No. 2, RV 279, keyFamily, minor mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyFamily Context triple: [Violin Concerto in E minor, Op. 4 No. 2, RV 279, keyFamily, minor mode]
-
A.
inKeyFamilyOf
chosen
Indicates that one musical key belongs to the same key family (e.g., closely related by key signature or tonal center) as another key.
-
B.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
-
C.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
D.
keyInterface
Indicates that one entity functions as the primary or main interface through which another entity is accessed or interacted with.
-
E.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.