Triple
T31570583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E805546
|
entity |
| Predicate | hasOpusOrCatalogNumber |
P66233
|
FINISHED |
| Object | varies by composer |
—
|
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: varies by composer | Statement: [Symphony No. 3, hasOpusOrCatalogNumber, varies by composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusOrCatalogNumber Context triple: [Symphony No. 3, hasOpusOrCatalogNumber, varies by composer]
-
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.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
D.
hasOpusGroup
Indicates that a work or composition belongs to, or is categorized within, a particular opus grouping or collection.
-
E.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 30, 2026, 10:19 p.m.