Triple
T13695330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBLS |
E328368
|
entity |
| Predicate | hasOnAirPersonalities |
P5272
|
FINISHED |
| Object | prominent DJs and hosts |
—
|
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: prominent DJs and hosts | Statement: [WBLS, hasOnAirPersonalities, prominent DJs and hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnAirPersonalities Context triple: [WBLS, hasOnAirPersonalities, prominent DJs and hosts]
-
A.
notableOnAirPersonality
chosen
Indicates that an entity is recognized as a prominent or distinguished on-air media personality associated with another entity (such as a show, station, or network).
-
B.
televisionAnnouncers
Indicates a relationship where certain people serve as announcers or presenters on television broadcasts.
-
C.
primeTimeAppearances
Indicates the number of times an entity has appeared in a prime-time broadcast or time slot.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
coHostOf
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8773f388190b2413b1e05fd5fd7 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.