Triple
T37922249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biamonti 247 |
E945994
|
entity |
| Predicate | relatedOpusNumber |
—
|
GENERATED |
| Object | Op. 27 No. 2 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedOpusNumber Context triple: [Biamonti 247, relatedOpusNumber, Op. 27 No. 2]
-
A.
hasOpusNumber
chosen
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.
partOfWorkByCatalogueNumber
Indicates that an item is a component or section of a larger work, identified specifically by its catalogue number.
-
C.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
D.
seriesNumberOfWorks
Indicates that an entity is assigned a specific position or sequence number within a series of related works.
-
E.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
- F. None of above.
Provenance (1 batch)
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.