Triple
T35982064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Radio Society of Regina Inc. |
E1040595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community radio organization |
C20591
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: community radio organization Context triple: [Community Radio Society of Regina Inc., instanceOf, community radio organization]
-
A.
campus-community radio station
A campus-community radio station is a non-profit, volunteer-driven broadcasting outlet affiliated with an educational institution that serves both the campus and surrounding community with diverse, locally relevant programming and opportunities for media participation.
-
B.
radio news organization
A radio news organization is an entity that gathers, produces, and broadcasts timely news and information content via radio and related audio platforms to inform and engage the public.
-
C.
community organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
D.
radio enthusiast organization
A radio enthusiast organization is a group that brings together individuals interested in radio communication to share knowledge, operate equipment, promote the hobby, and support community and emergency communication activities.
-
E.
radio broadcasting company
A radio broadcasting company is an organization that produces, transmits, and distributes audio content over radio frequencies or digital streams to reach and engage a listening audience.
- F. None of above.
Provenance (1 batch)
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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.