Triple
T834229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stockholm Philharmonic Orchestra |
E18033
|
entity |
| Predicate | hasRepertoire |
P3738
|
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: [Royal Stockholm Philharmonic Orchestra, hasRepertoire, classical repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepertoire Context triple: [Royal Stockholm Philharmonic Orchestra, hasRepertoire, classical repertoire]
-
A.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
C.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
D.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
E.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.