Triple
T3377271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The One Show |
E71093
|
entity |
| Predicate | hasBroadcastFrequency |
P48082
|
FINISHED |
| Object | weekdays |
—
|
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: weekdays | Statement: [The One Show, hasBroadcastFrequency, weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastFrequency Context triple: [The One Show, hasBroadcastFrequency, weekdays]
-
A.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
B.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
C.
broadcastFrequency
Indicates the specific radio or transmission frequency at which a broadcast is sent or received.
-
D.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
E.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:13 p.m.