Triple
T28699622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Canada |
E729512
|
entity |
| Predicate | linearChannel |
P165235
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BBC Canada, linearChannel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linearChannel Context triple: [BBC Canada, linearChannel, yes]
-
A.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
-
B.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
C.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
D.
typicalChannel
Indicates the usual or most commonly used communication or distribution channel through which an interaction, message, or transaction typically occurs.
-
E.
closedAsLinearChannel
Indicates that one entity has been closed or terminated by being converted into or treated as a linear (one-way, sequential) communication channel.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:41 a.m.