Triple
T11775388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus 27 No. 2 |
E280004
|
entity |
| Predicate | numberWithinOpus |
P89977
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Opus 27 No. 2, numberWithinOpus, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberWithinOpus Context triple: [Opus 27 No. 2, numberWithinOpus, 2]
-
A.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
B.
numberWithinClass
chosen
Indicates that an entity has a specific numerical value or position that is defined relative to a particular class or category it belongs to.
-
C.
movementCountPerOpus
Indicates the number of movements associated with each opus.
-
D.
numberInInstrument
Indicates that an entity specifies the count or quantity of items contained within or associated with a particular instrument.
-
E.
hasOpusGroup
Indicates that a work or composition belongs to, or is categorized within, a particular opus grouping or collection.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:41 p.m.