Triple
T8988885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Lie |
E214736
|
entity |
| Predicate | hasRadioRelease |
P86185
|
FINISHED |
| Object | urban contemporary radio |
—
|
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: urban contemporary radio | Statement: [No Lie, hasRadioRelease, urban contemporary radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioRelease Context triple: [No Lie, hasRadioRelease, urban contemporary radio]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
C.
hasRadioShow
Indicates that an entity hosts, produces, or is responsible for a radio show.
-
D.
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.
-
E.
hasLiveAlbumReleaseType
Indicates that a musical work or recording has a release type specifically classified as a live album.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67f0fed8819098ef3c88f9ef8045 |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:04 p.m.