Triple
T11483479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Radio Scotland |
E272214
|
entity |
| Predicate | hasProgrammeFormat |
P41755
|
FINISHED |
| Object | phone-in |
—
|
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: phone-in | Statement: [BBC Radio Scotland, hasProgrammeFormat, phone-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammeFormat Context triple: [BBC Radio Scotland, hasProgrammeFormat, phone-in]
-
A.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
B.
offersProgramFormat
chosen
Indicates that an entity provides or makes available a specific type or format of program.
-
C.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
D.
hasGlobalProgramme
Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
-
E.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
- F. None of above.
Provenance (3 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a1d86b88190b180f6b0d0a27029 |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.