Triple
T23754570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 4 |
E587068
|
entity |
| Predicate | textAuthorOfFinale |
P153561
|
FINISHED |
| Object | Des Knaben Wunderhorn |
—
|
NE NERFINISHED |
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: Des Knaben Wunderhorn | Statement: [Mahler Symphony No. 4, textAuthorOfFinale, Des Knaben Wunderhorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textAuthorOfFinale Context triple: [Mahler Symphony No. 4, textAuthorOfFinale, Des Knaben Wunderhorn]
-
A.
finaleCharacter
Indicates that the specified character appears or plays a significant role in the final part or ending segment of a work or event.
-
B.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
-
C.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
D.
keyOfFinale
Indicates the musical key in which the final or last movement/section of a work is set.
-
E.
literarySeriesFinaleOf
Indicates that one work is the concluding or final installment of a particular literary series.
- F. None of above. chosen
Provenance (4 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc561b081908bfd516ef5e2dcfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:13 p.m.