Triple
T23872017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uf dem Anger |
E592751
|
entity |
| Predicate | workNumberWithinCarminaBurana |
P83262
|
FINISHED |
| Object | central group of movements |
—
|
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: central group of movements | Statement: [Uf dem Anger, workNumberWithinCarminaBurana, central group of movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberWithinCarminaBurana Context triple: [Uf dem Anger, workNumberWithinCarminaBurana, central group of movements]
-
A.
workNumberInPaganiniOutput
Indicates that a work is identified by a specific catalog or opus number within the standardized output of Paganini’s compositions.
-
B.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
C.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
D.
numberInAnthology
chosen
Indicates the specific position or sequence number that a work occupies within an anthology.
-
E.
workNumberWithinOratorio
Indicates that a specific work is identified by its numerical position within an oratorio.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.