Triple
T14283484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pobol y Cwm |
E354108
|
entity |
| Predicate | hasRegularBroadcastFrequency |
P113603
|
FINISHED |
| Object | multiple episodes per week |
—
|
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: multiple episodes per week | Statement: [Pobol y Cwm, hasRegularBroadcastFrequency, multiple episodes per week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularBroadcastFrequency Context triple: [Pobol y Cwm, hasRegularBroadcastFrequency, multiple episodes per week]
-
A.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
B.
isFrequentlyBroadcastDuring
Indicates that one entity (such as a program, advertisement, or message) is regularly aired or transmitted during another entity (such as a specific time slot, event, or show).
-
C.
broadcastFrequencyType
Indicates the type or category of frequency used for broadcasting a signal or transmission.
-
D.
broadcastFrequency
Indicates the specific radio or transmission frequency at which a broadcast is sent or received.
-
E.
typicalBroadcastPeriod
Indicates the usual or standard time interval during which something is broadcast or transmitted.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697d9fd08190b0cd7a6a6737ba03 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.