Triple
T30429166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDR10+ |
E774111
|
entity |
| Predicate | logoProgramFor |
P14759
|
FINISHED |
| Object | certified HDR10+ devices |
—
|
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: certified HDR10+ devices | Statement: [HDR10+, logoProgramFor, certified HDR10+ devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logoProgramFor Context triple: [HDR10+, logoProgramFor, certified HDR10+ devices]
-
A.
logoProgram
chosen
Indicates that an entity serves as the logo or emblem used in a specific program, application, or software.
-
B.
programOf
Indicates that one entity is a program (such as a course of study or curriculum) that is offered, managed, or associated with another entity (such as an institution, department, or organization).
-
C.
flagshipProgram
Indicates that a program is the primary, most prominent, or most important offering associated with an entity.
-
D.
agencyProgramme
Indicates that an agency is responsible for, manages, or is associated with a particular programme.
-
E.
companyProgram
Indicates that a program is organized, operated, or sponsored by a specific company.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866aa9f88190b3e139fb374d6606 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:06 p.m.