Triple
T29576480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Pieces for Orchestra, Op. 6 |
E753456
|
entity |
| Predicate | movementTitle3 |
P172397
|
FINISHED |
| Object | Marsch |
—
|
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: Marsch | Statement: [Three Pieces for Orchestra, Op. 6, movementTitle3, Marsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementTitle3 Context triple: [Three Pieces for Orchestra, Op. 6, movementTitle3, Marsch]
-
A.
movement2Title
Indicates a relationship where a specific movement, action, or motion is associated with or labeled by a particular title or name.
-
B.
movementNumber3Title
Indicates the specific title assigned to the third movement within a larger multi-movement work.
-
C.
movement1Title
Indicates the title or descriptive label assigned to a specific movement within a larger work or sequence.
-
D.
movement5Title
Indicates the title or label assigned to the fifth movement in a sequence of movements.
-
E.
movementName
Indicates the specific title or designation assigned to a particular movement or action.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 28, 2026, 6:03 p.m.