Triple

T36735541
Position Surface form Disambiguated ID Type / Status
Subject Andrzej Panufnik E907461 entity
Predicate notableWork P4 FINISHED
Object Sinfonia Votiva
Sinfonia Votiva is a symphonic work by Polish-British composer Andrzej Panufnik, known for its spiritual character and reflection on Polish history and identity.
E2200024 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: Sinfonia Votiva | Statement: [Andrzej Panufnik, notableWork, Sinfonia Votiva]
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: Sinfonia Votiva
Triple: [Andrzej Panufnik, notableWork, Sinfonia Votiva]
Generated description
Sinfonia Votiva is a symphonic work by Polish-British composer Andrzej Panufnik, known for its spiritual character and reflection on Polish history and identity.

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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c8fa6d8c8190b6bcd59c60ad2503 completed May 3, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3d179000a48190ac074a008c1fba44 completed June 25, 2026, 11:57 a.m.
NEDg Description generation batch_6a3d1b684f048190a3280d0e401094f0 completed June 25, 2026, 12:13 p.m.
NED2 Entity disambiguation (via description) batch_6a3dd0510f40819097a3c356f1b3b83a completed June 26, 2026, 1:05 a.m.
Created at: May 3, 2026, 4:12 p.m.