Triple
T38080469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirtengesang – Frohe und dankbare Gefühle nach dem Sturm |
E950837
|
entity |
| Predicate | precededByMovementNumber |
P196449
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Hirtengesang – Frohe und dankbare Gefühle nach dem Sturm, precededByMovementNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByMovementNumber Context triple: [Hirtengesang – Frohe und dankbare Gefühle nach dem Sturm, precededByMovementNumber, 4]
-
A.
precededByMovement
Indicates that an event or state occurs only after a prior movement action has taken place.
-
B.
hasMovementBefore
Indicates that one movement or motion event occurs earlier in time than another movement or motion event.
-
C.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
D.
successorInMovement
Indicates that one movement directly follows another in a sequence or progression.
-
E.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:21 p.m.