Triple

T167261
Position Surface form Disambiguated ID Type / Status
Subject Boston Symphony Orchestra E3042 entity
Predicate musicDirectorStart P5558 FINISHED
Object 2014 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: 2014 | Statement: [Boston Symphony Orchestra, musicDirectorStart, 2014]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: musicDirectorStart
Context triple: [Boston Symphony Orchestra, musicDirectorStart, 2014]
  • A. musicBy
    Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
  • B. originalConductor
    Indicates that an entity served as the first or initial conductor responsible for leading or directing a particular performance, ensemble, or musical work.
  • C. orchestrator
    Indicates coordinating and directing the actions or interactions of multiple entities to achieve a unified outcome.
  • D. director
    Indicates that one entity serves as the director (creative or managerial leader) of another entity, such as a film, organization, or project.
  • E. hasNotableRecordingBy
    Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
  • 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_69a2524ce1e48190ab066bf72859f474 completed Feb. 28, 2026, 2:26 a.m.
NER Named-entity recognition batch_69a25884c8d88190bc4cb4e3541e8116 completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a25665f5b8819096ca3e084faf976e completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a257101060819094db0f3a3a72f312 completed Feb. 28, 2026, 2:46 a.m.
Created at: Feb. 28, 2026, 2:34 a.m.