Triple

T26038853
Position Surface form Disambiguated ID Type / Status
Subject Seattle Symphony E647627 entity
Predicate hasFormerMusicDirector P12174 FINISHED
Object Anshel Brusilow
Anshel Brusilow was an American violinist and conductor known for his leadership roles with major orchestras and his influential work as a music educator.
E1710857 NE 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: Anshel Brusilow | Statement: [Seattle Symphony, hasFormerMusicDirector, Anshel Brusilow]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Anshel Brusilow
Triple: [Seattle Symphony, hasFormerMusicDirector, Anshel Brusilow]
Generated description
Anshel Brusilow was an American violinist and conductor known for his leadership roles with major orchestras and his influential work as a music educator.

Provenance (5 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_69e77e8c88f08190858c4c81bd2e1b9a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f60620fb648190826cfb2fdefe4858 completed May 2, 2026, 2:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11273fac2c81908d1efa7a9d3ea2fc completed May 23, 2026, 4:04 a.m.
NEDg Description generation batch_6a1153d6dd608190bd02f3f15210f929 completed May 23, 2026, 7:14 a.m.
NED2 Entity disambiguation (via description) batch_6a1155021a8c8190acf7aa793cf0f3c3 completed May 23, 2026, 7:19 a.m.
Created at: April 22, 2026, 9:08 a.m.