Triple
T12159811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrapunctus X |
E289673
|
entity |
| Predicate | movementNumberWithinWork |
P12040
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Contrapunctus X, movementNumberWithinWork, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementNumberWithinWork Context triple: [Contrapunctus X, movementNumberWithinWork, 10]
-
A.
movementNumber
chosen
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
B.
movementNumberInOp130
Indicates the specific movement number of a work within Opus 130.
-
C.
movementOfWorkInThisKey
Indicates that a work or task is being transferred, reassigned, or progressed within the context of a specific key, category, or workflow state.
-
D.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
E.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.