Triple
T4212092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDR Symphony Orchestra |
E93924
|
entity |
| Predicate | hasArtisticRole |
P9640
|
FINISHED |
| Object | interpreting classical works |
—
|
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: interpreting classical works | Statement: [NDR Symphony Orchestra, hasArtisticRole, interpreting classical works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticRole Context triple: [NDR Symphony Orchestra, hasArtisticRole, interpreting classical works]
-
A.
hasArtisticDiscipline
Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
-
B.
hasArtistRole
chosen
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
C.
hasArtisticReputation
Indicates that an entity is recognized or regarded for its artistic skill, contribution, or standing.
-
D.
hasArtisticGenre
Indicates that an entity (such as a work or creation) belongs to or is characterized by a particular artistic genre.
-
E.
hasArtisticFocus
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.