Triple
T632822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC iPlayer |
E15957
|
entity |
| Predicate | streamingProtocol |
P15185
|
FINISHED |
| Object | HTTP adaptive streaming |
—
|
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: HTTP adaptive streaming | Statement: [BBC iPlayer, streamingProtocol, HTTP adaptive streaming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamingProtocol Context triple: [BBC iPlayer, streamingProtocol, HTTP adaptive streaming]
-
A.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
streamingService
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
C.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
D.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
transmissionStandard
chosen
Indicates the communication or signal protocol used to transmit data or content between systems or devices.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec2a4c08190bc5c6ce8a10b0967 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.