Triple
T26194148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KWKH |
E655049
|
entity |
| Predicate | hasAnnouncers |
P168050
|
FINISHED |
| Object | radio announcers |
—
|
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: radio announcers | Statement: [KWKH, hasAnnouncers, radio announcers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnouncers Context triple: [KWKH, hasAnnouncers, radio announcers]
-
A.
hasAnnouncementsSystem
Indicates that an entity is equipped with or uses a system for creating, managing, and delivering announcements.
-
B.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
C.
hasPartyAnnouncements
Indicates that there exist announcements or notifications associated with a particular party or event.
-
D.
hasRingAnnouncer
Indicates that an event, typically a combat or sports match, is associated with a specific ring announcer who introduces participants and makes formal announcements.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 26, 2026, 8:45 p.m.