Triple
T32061914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HLS |
E818767
|
entity |
| Predicate | drmEcosystem |
P173166
|
FINISHED |
| Object | FairPlay Streaming |
—
|
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: FairPlay Streaming | Statement: [HLS, drmEcosystem, FairPlay Streaming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drmEcosystem Context triple: [HLS, drmEcosystem, FairPlay Streaming]
-
A.
technologyEcosystem
Indicates the relationship in which technologies, organizations, and users interact and depend on each other as part of a broader, interconnected technological environment.
-
B.
hasAccessoryEcosystem
Indicates that an entity is associated with a surrounding set of compatible accessories, add-ons, or peripheral products designed to work with it.
-
C.
platformShowcased
Indicates that a platform is prominently presented or highlighted, typically to draw attention to its features, capabilities, or offerings.
-
D.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
-
E.
platformAdopted
Indicates that an entity has begun using or officially implemented 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f638908190957f64096c07535f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:22 a.m.