Triple

T27531972
Position Surface form Disambiguated ID Type / Status
Subject Bergen Philharmonic Orchestra E694994 entity
Predicate hasHonoraryConductor P79441 FINISHED
Object Andrew Litton 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: Andrew Litton | Statement: [Bergen Philharmonic Orchestra, hasHonoraryConductor, Andrew Litton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHonoraryConductor
Context triple: [Bergen Philharmonic Orchestra, hasHonoraryConductor, Andrew Litton]
  • A. honoraryConductor chosen
    Indicates that a person holds an honorary (non-regular, often ceremonial) conductor role with an orchestra or musical ensemble.
  • B. hasConductor
    Indicates that an entity (such as an event, performance, or ensemble) is associated with a specific conductor who leads or directs it.
  • C. notableConductor
    Indicates that the subject is a conductor who is recognized as notable or distinguished in their field.
  • D. principalGuestConductorOf
    Indicates that one entity serves as the principal guest conductor for another entity, typically an orchestra or musical ensemble.
  • E. notableRecordingConductor
    Indicates that the object is a conductor who is notably associated with conducting a particular recording of the subject work or performance.
  • 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_69ef538608b081908b9f659bb09d5e0f completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f71f8ee0688190bd025f27993452d3 completed May 3, 2026, 10:12 a.m.
PD Predicate disambiguation batch_69f71cc405c08190863565609a4c8499 completed May 3, 2026, 10 a.m.
Created at: April 27, 2026, 1:26 p.m.