Triple
T37882513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Broadcasting |
E944903
|
entity |
| Predicate | operatedRadioBrand |
P32898
|
FINISHED |
| Object | Rogers Radio |
E918150
|
NE 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: Rogers Radio | Statement: [Rogers Broadcasting, operatedRadioBrand, Rogers Radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRadioBrand Context triple: [Rogers Broadcasting, operatedRadioBrand, Rogers Radio]
-
A.
operatedChannelBrand
Indicates that a brand is responsible for operating or managing a particular channel.
-
B.
operatedByBrand
chosen
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
C.
operatorBrandNameFor
Indicates that a given brand name is used as the commercial or public-facing name for a particular operator.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- F. None of above.
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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a031b40c6d0819096f4b9787a1f09d1 |
completed | May 12, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4104316e1c8190aecb8293ed0d56dd |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a03191f8ee08190b3416b044869ddfd |
completed | May 12, 2026, 12:12 p.m. |
Created at: May 3, 2026, 4:19 p.m.