Triple
T21406018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sure Be Cool If You Did |
E528034
|
entity |
| Predicate | releasedToRadioOn |
P86185
|
FINISHED |
| Object | 2013-01-14 |
—
|
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: 2013-01-14 | Statement: [Sure Be Cool If You Did, releasedToRadioOn, 2013-01-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedToRadioOn Context triple: [Sure Be Cool If You Did, releasedToRadioOn, 2013-01-14]
-
A.
hasRadioRelease
chosen
Indicates that an entity was released or made available specifically for radio broadcast.
-
B.
releasedSong
Indicates that an artist or entity has made a particular song publicly available, typically as a publication or distribution event.
-
C.
releasedMusicBy
Indicates that a musical work (such as a song, album, or EP) was issued or made publicly available by a particular artist or musical act.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
releasedThrough
Indicates that something (such as a work, product, or content) is made publicly available or distributed via a particular channel, platform, or intermediary.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62d01634819089dd64fe7bc5ccbd |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:31 p.m.