Triple
T2434517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert-Schumann-Philharmonie |
E52923
|
entity |
| Predicate | repertoireFocus |
P20265
|
FINISHED |
| Object | classical repertoire |
—
|
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: classical repertoire | Statement: [Robert-Schumann-Philharmonie, repertoireFocus, classical repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repertoireFocus Context triple: [Robert-Schumann-Philharmonie, repertoireFocus, classical repertoire]
-
A.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
musicFocus
chosen
Indicates that the primary attention or emphasis is directed toward music or musical aspects.
-
C.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
D.
primaryInstrumentalFocus
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.