Triple
T2232750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serenade for Strings in C major, Op. 48 |
E49207
|
entity |
| Predicate | composedInYear |
P10580
|
FINISHED |
| Object | 1880 |
—
|
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: 1880 | Statement: [Serenade for Strings in C major, Op. 48, composedInYear, 1880]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedInYear Context triple: [Serenade for Strings in C major, Op. 48, composedInYear, 1880]
-
A.
compositionYear
chosen
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
-
B.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
C.
formedInYear
Indicates the year in which an entity was originally established, created, or came into existence.
-
D.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
E.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06d26bc8190a85ddb6312d2df08 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.