Triple
T32459299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Love a Piano |
E829519
|
entity |
| Predicate | hasSheetMusicCoverArtFeaturing |
P15267
|
FINISHED |
| Object | piano imagery |
—
|
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 imagery | Statement: [I Love a Piano, hasSheetMusicCoverArtFeaturing, piano imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSheetMusicCoverArtFeaturing Context triple: [I Love a Piano, hasSheetMusicCoverArtFeaturing, piano imagery]
-
A.
hasSheetMusicAvailability
Indicates that there exists accessible sheet music associated with the referenced musical work or performance.
-
B.
hasCoverArtFeaturing
chosen
Indicates that one entity’s cover art visually features or depicts another entity.
-
C.
isCoverArtFor
Indicates that one item serves as the cover artwork or visual representation for another item, such as a publication, recording, or product.
-
D.
musicScoreBy
Indicates that a musical score was created or composed by a particular agent or entity.
-
E.
hasNoMusicalScore
Indicates that something lacks an associated musical score or written musical accompaniment.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 12:57 a.m.