Triple
T2872545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Philharmonic |
E56796
|
entity |
| Predicate | hasNoPrincipalConductor |
P43445
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vienna Philharmonic, hasNoPrincipalConductor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoPrincipalConductor Context triple: [Vienna Philharmonic, hasNoPrincipalConductor, true]
-
A.
hasConductor
Indicates that an entity (such as an event, performance, or ensemble) is associated with a specific conductor who leads or directs it.
-
B.
principalConductor
Indicates that one entity serves as the main or lead conductor for another entity, typically an orchestra or musical ensemble.
-
C.
originalConductor
Indicates that an entity served as the first or initial conductor responsible for leading or directing a particular performance, ensemble, or musical work.
-
D.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
E.
principalGuestConductorOf
Indicates that one entity serves as the principal guest conductor for another entity, typically an orchestra or musical ensemble.
- F. None of above. chosen
Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abdfe59ef88190b8bdfdd03e8965f3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:03 p.m.