Triple
T11861888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirtengesang. Frohe und dankbare Gefühle nach dem Sturm |
E282178
|
entity |
| Predicate | hasSectionOfWorkType |
P101914
|
FINISHED |
| Object | coda |
—
|
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: coda | Statement: [Hirtengesang. Frohe und dankbare Gefühle nach dem Sturm, hasSectionOfWorkType, coda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectionOfWorkType Context triple: [Hirtengesang. Frohe und dankbare Gefühle nach dem Sturm, hasSectionOfWorkType, coda]
-
A.
appearsInSectionOfWork
Indicates that one entity is contained within or shows up in a specific section or part of a larger work.
-
B.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
C.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
-
D.
hasWorkField
Indicates that an entity is associated with or operates within a particular field or area of work.
-
E.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
- 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_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. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.