Triple
T31391256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisongs |
E800737
|
entity |
| Predicate | hasPublishingRightsForSong |
P136869
|
FINISHED |
| Object | My Sweet Lord |
—
|
NE NERFINISHED |
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: My Sweet Lord | Statement: [Harrisongs, hasPublishingRightsForSong, My Sweet Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublishingRightsForSong Context triple: [Harrisongs, hasPublishingRightsForSong, My Sweet Lord]
-
A.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
B.
publishingCatalogIncludesSong
chosen
Indicates that a music publishing catalog contains or lists a particular song as part of its works.
-
C.
hasSongwriterWithUnverifiedCredit
Indicates that an entity is associated with a songwriter whose authorship credit exists but has not been fully verified or confirmed.
-
D.
musicPublishingArm
Indicates that one entity serves as the music publishing division or subsidiary of another entity, handling rights and administration of musical works on its behalf.
-
E.
isLiveVersionOfSongBy
Indicates that one entity is a live performance version of a song that was originally created or performed by another 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 9:19 p.m.