Triple
T8763905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Man |
E208275
|
entity |
| Predicate | signatureLyric |
P85250
|
FINISHED |
| Object | Sing us a song, you’re the piano man |
—
|
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: Sing us a song, you’re the piano man | Statement: [Piano Man, signatureLyric, Sing us a song, you’re the piano man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureLyric Context triple: [Piano Man, signatureLyric, Sing us a song, you’re the piano man]
-
A.
signatureTuneOf
Indicates that one entity is the characteristic or officially recognized musical theme associated with another entity.
-
B.
isSignatureSongOf
Indicates that a particular song is widely recognized as the most iconic or defining song associated with a specific artist or group.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signedByArtist
Indicates that an item, such as a work or object, bears the authentic signature of the specified artist.
-
E.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfdef9881908a7f079d87e8e338 |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:40 p.m.