Triple
T11861809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szene am Bach |
E282176
|
entity |
| Predicate | workNumberInOpus |
P32662
|
FINISHED |
| Object | second movement of Op. 68 |
—
|
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: second movement of Op. 68 | Statement: [Szene am Bach, workNumberInOpus, second movement of Op. 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInOpus Context triple: [Szene am Bach, workNumberInOpus, second movement of Op. 68]
-
A.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
B.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
C.
workNumberInDeRePublica
Indicates that an entity has a specific work number or index within the collection or edition of "De Re Publica."
-
D.
workNumberInComposerOutput
chosen
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
E.
workOpus
Indicates that an entity is the creator or author of a particular work or opus.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.