Triple
T22814532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Source Extensions |
E565064
|
entity |
| Predicate | usedWith |
P4791
|
FINISHED |
| Object | hls.js |
—
|
NE NERFINISHED |
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: hls.js | Statement: [Media Source Extensions, usedWith, hls.js]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: hls.js Context triple: [Media Source Extensions, usedWith, hls.js]
-
A.
HLS
HLS is the standardized high-level framework that harmonizes the structure and core requirements of ISO management system standards across different disciplines.
-
B.
HLS
chosen
HLS (HTTP Live Streaming) is Apple’s adaptive bitrate streaming protocol widely used for delivering live and on-demand audio and video over the internet.
-
C.
HLS
HLS is the station code for Hillsdale station, a commuter rail stop serving the Hillsdale area.
-
D.
HLS
HLS is the National Rail station code for Hilsea railway station in Portsmouth, England.
-
E.
MPEG-DASH
MPEG-DASH is an international standard for adaptive bitrate streaming of multimedia content over HTTP, enabling high-quality video delivery across varying network conditions and devices.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
Created at: April 17, 2026, 3:33 p.m.