Triple
T18419701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Footsteps in the Dark |
E441988
|
entity |
| Predicate | isRadioStapleOn |
P110262
|
FINISHED |
| Object | quiet storm radio formats |
—
|
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: quiet storm radio formats | Statement: [Footsteps in the Dark, isRadioStapleOn, quiet storm radio formats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRadioStapleOn Context triple: [Footsteps in the Dark, isRadioStapleOn, quiet storm radio formats]
-
A.
isClassicRockRadioStaple
Indicates that a song is frequently played and widely recognized as a standard selection on classic rock radio stations.
-
B.
isRadioHit
chosen
Indicates that a song or track has achieved significant popularity and frequent airplay on radio stations.
-
C.
isRadioFriendly
Indicates that something (typically a song, track, or audio content) is suitable for broadcast on mainstream radio, usually by meeting content, length, and formatting standards.
-
D.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
E.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a2b0f0481909c3995bf532162a3 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.