Triple
T10954389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Ago (and Far Away) |
E258804
|
entity |
| Predicate | hasSheetMusicFormat |
P24751
|
FINISHED |
| Object | piano-vocal |
—
|
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-vocal | Statement: [Long Ago (and Far Away), hasSheetMusicFormat, piano-vocal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSheetMusicFormat Context triple: [Long Ago (and Far Away), hasSheetMusicFormat, piano-vocal]
-
A.
hasSheetMusicAvailability
chosen
Indicates that there exists accessible sheet music associated with the referenced musical work or performance.
-
B.
musicScoreBy
Indicates that a musical score was created or composed by a particular agent or entity.
-
C.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
hasPianoAccompaniment
Indicates that something (such as a musical work or performance) is accompanied by a piano part.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ff718c81909d4baebea3b56b83 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.