Triple
T1231228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero (song) |
E26445
|
entity |
| Predicate | hasSheetMusicAvailability |
P24751
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hero (song), hasSheetMusicAvailability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSheetMusicAvailability Context triple: [Hero (song), hasSheetMusicAvailability, yes]
-
A.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
B.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
C.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
D.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
E.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
- F. None of above. chosen
Provenance (4 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5a25348190a0665b6324c4d8f5 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.