Triple
T18742580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Baby |
E458326
|
entity |
| Predicate | hasRadioAirplay |
P19932
|
FINISHED |
| Object | heavy rotation on US rock 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: heavy rotation on US rock radio | Statement: [American Baby, hasRadioAirplay, heavy rotation on US rock radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioAirplay Context triple: [American Baby, hasRadioAirplay, heavy rotation on US rock radio]
-
A.
hasNotableAirplay
chosen
Indicates that something (typically a song, program, or audio content) has received a significant amount of broadcast play on radio or similar media.
-
B.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
-
C.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
-
D.
isRadioHit
Indicates that a song or track has achieved significant popularity and frequent airplay on radio stations.
-
E.
supportsAirPlay
Indicates that one entity is capable of sending or receiving media via Apple’s AirPlay streaming protocol in relation to 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768fc1f8819085a2abf129ade34b |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.