Triple
T37611822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanze in F major, Op. 118 No. 5 |
E935802
|
entity |
| Predicate | hasPublisherCategory |
P59457
|
FINISHED |
| Object | piano solo sheet music |
—
|
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: piano solo sheet music | Statement: [Romanze in F major, Op. 118 No. 5, hasPublisherCategory, piano solo sheet music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublisherCategory Context triple: [Romanze in F major, Op. 118 No. 5, hasPublisherCategory, piano solo sheet music]
-
A.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
B.
publishesCategory
chosen
Indicates that an entity (such as a publisher or platform) makes content belonging to a particular category publicly available.
-
C.
hasBibliographicCategory
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
-
D.
hasPublisherBackground
Indicates that an entity has a background or prior experience as a publisher.
-
E.
hasPublishingLabelType
Indicates the type or category of publishing label associated with an entity.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:18 p.m.