Triple
T22520021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphoniae sacrae I |
E556748
|
entity |
| Predicate | composer |
P1361
|
FINISHED |
| Object | Heinrich Schütz |
—
|
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: Heinrich Schütz | Statement: [Symphoniae sacrae I, composer, Heinrich Schütz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinrich Schütz Context triple: [Symphoniae sacrae I, composer, Heinrich Schütz]
-
A.
Heinrich Schütz
chosen
Heinrich Schütz was a seminal early Baroque German composer whose sacred and secular vocal works helped lay the foundations for German music before Bach.
-
B.
Friedrich Schütz
Friedrich Schütz was an Austrian writer and journalist known for his contributions to 19th-century German-language literature and press.
-
C.
Hans Schütz
Hans Schütz is a relatively obscure individual whose name is notably recorded as a bearer of the surname Schütz.
-
D.
Reinhard Keiser
Reinhard Keiser was a prominent German Baroque composer best known for his influential operas and leadership in early 18th-century Hamburg’s opera scene.
-
E.
Günther Schütz
Günther Schütz is a notable individual who shares the surname Schütz, recognized enough to be specifically cited as a bearer of the name.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e31f43c8190899f5e35b150fe85 |
completed | April 29, 2026, 1:26 a.m. |
Created at: April 16, 2026, 8:50 p.m.