Triple
T2577281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missa solemnis in D major, Op. 123 |
E57005
|
entity |
| Predicate | compositionEnd |
P20250
|
FINISHED |
| Object | 1823 |
—
|
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: 1823 | Statement: [Missa solemnis in D major, Op. 123, compositionEnd, 1823]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionEnd Context triple: [Missa solemnis in D major, Op. 123, compositionEnd, 1823]
-
A.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
B.
composedFor
Indicates that a creative work (typically a piece of music) was specifically written or created for a particular person, group, event, or purpose.
-
C.
compositionChanged
Indicates that the makeup or constituent elements of something have been altered from a previous state.
-
D.
composedIn
chosen
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
E.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.