Triple
T10528492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Élégie |
E248368
|
entity |
| Predicate | workKeyContext |
P40856
|
FINISHED |
| Object | C major (overall serenade key) |
—
|
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: C major (overall serenade key) | Statement: [III. Élégie, workKeyContext, C major (overall serenade key)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workKeyContext Context triple: [III. Élégie, workKeyContext, C major (overall serenade key)]
-
A.
keyOfWork
chosen
Indicates that one entity specifies the musical key in which a particular work is composed or performed.
-
B.
workIsKeySourceFor
Indicates that the referenced work serves as a primary or crucial source of information, evidence, or inspiration for the associated entity.
-
C.
keyWorkOf
Indicates that the subject is a central, defining, or most important work created by the object (such as an artist, author, or creator).
-
D.
laborContext
Indicates the labor-related circumstances, conditions, or setting within which an action, relationship, or event takes place.
-
E.
primaryWorkContext
Indicates the main environment, setting, or domain in which an entity typically performs its work or primary activities.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f6f4a88190ae6e0cc0bcbff0c5 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.