Triple
T32805547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forellenquintett |
E839010
|
entity |
| Predicate | hasOpusOrCatalogueNumber |
P66233
|
FINISHED |
| Object | D. 667 |
—
|
NE NERFINISHED |
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: D. 667 | Statement: [Forellenquintett, hasOpusOrCatalogueNumber, D. 667]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusOrCatalogueNumber Context triple: [Forellenquintett, hasOpusOrCatalogueNumber, D. 667]
-
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.
hasOpusForm
Indicates that an entity (such as a work or composition) is associated with a specific opus form or cataloging format.
-
C.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
D.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
E.
isDiscographyOf
Indicates that one entity is the complete collection of recorded works (discography) belonging to another entity, typically an artist or band.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:15 a.m.