Triple
T6101117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix Mendelssohn's A Midsummer Night's Dream |
E135996
|
entity |
| Predicate | incidentalMusicComposedInYear |
P10580
|
FINISHED |
| Object | 1842 |
—
|
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: 1842 | Statement: [Felix Mendelssohn's A Midsummer Night's Dream, incidentalMusicComposedInYear, 1842]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentalMusicComposedInYear Context triple: [Felix Mendelssohn's A Midsummer Night's Dream, incidentalMusicComposedInYear, 1842]
-
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.
circaComposition
Indicates that one entity was composed or created around, but not exactly on, the time associated with another entity.
-
C.
recordingYear
Indicates the specific calendar year in which something (such as audio, video, or data) was recorded.
-
D.
musicComposedIn
Indicates that a piece of music was created or composed in a specific place or location.
-
E.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3aa9908190865be98ada141d37 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.