Triple
T35114693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasted |
E1013399
|
entity |
| Predicate | releaseAsSingleFromAlbum |
P49151
|
FINISHED |
| Object | Some Hearts |
—
|
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: Some Hearts | Statement: [Wasted, releaseAsSingleFromAlbum, Some Hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseAsSingleFromAlbum Context triple: [Wasted, releaseAsSingleFromAlbum, Some Hearts]
-
A.
releasedAsSingleIn
Indicates that a musical work or track was issued as a standalone single in a specific year or time period.
-
B.
releasedAsSingleFor
chosen
Indicates that a particular track or song was issued as a standalone single specifically to promote or represent a given album, project, or release.
-
C.
isNonAlbumSingleFrom
Indicates that a song or track was released as a standalone single and does not belong to the referenced album.
-
D.
releasedOnAlbum
Indicates that a musical work (such as a song or track) was issued as part of a specific album.
-
E.
releasedAsSingleInTerritory
Indicates that a work (such as a song or recording) was issued as a single in a specific geographic territory or market.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:01 p.m.