Triple
T2918254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Radio and Music |
E78657
|
entity |
| Predicate | platformIncludes |
P43902
|
FINISHED |
| Object | linear radio |
—
|
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: linear radio | Statement: [BBC Radio and Music, platformIncludes, linear radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformIncludes Context triple: [BBC Radio and Music, platformIncludes, linear radio]
-
A.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
B.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
C.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
D.
hardwareIncluded
Indicates that certain hardware components are provided or come bundled together with another item or product.
-
E.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:54 p.m.