Triple
T11753248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosse Fuge, Op. 133 |
E279458
|
entity |
| Predicate | movementNumberInOp130 |
P101170
|
FINISHED |
| Object | sixth movement |
—
|
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: sixth movement | Statement: [Grosse Fuge, Op. 133, movementNumberInOp130, sixth movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberInOp130 Context triple: [Grosse Fuge, Op. 133, movementNumberInOp130, sixth movement]
-
A.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
B.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
C.
movementNumber3Title
Indicates the specific title assigned to the third movement within a larger multi-movement work.
-
D.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
E.
movement3Key
Indicates a three-part or third-level categorization of how an entity moves or changes location relative to another entity or reference point.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.