Triple
T30690871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony: Mathis der Maler |
E781322
|
entity |
| Predicate | movementEnglishTitle |
P39539
|
FINISHED |
| Object | Angelic Concert |
—
|
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: Angelic Concert | Statement: [Symphony: Mathis der Maler, movementEnglishTitle, Angelic Concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementEnglishTitle Context triple: [Symphony: Mathis der Maler, movementEnglishTitle, Angelic Concert]
-
A.
movementAlsoKnownAs
Indicates that a movement is referred to by an alternative name or alias.
-
B.
movement1Title
chosen
Indicates the title or descriptive label assigned to a specific movement within a larger work or sequence.
-
C.
movement5Title
Indicates the title or label assigned to the fifth movement in a sequence of movements.
-
D.
movement2Title
Indicates a relationship where a specific movement, action, or motion is associated with or labeled by a particular title or name.
-
E.
notableEnglishProduction
Indicates that an entity has a significant or well-known production (such as a performance, adaptation, or staging) specifically in the English language.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 29, 2026, 8:33 p.m.