Triple
T2987489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Vision |
E80660
|
entity |
| Predicate | profileExample |
P41733
|
FINISHED |
| Object | Profile 5 (single-layer, streaming-focused) |
—
|
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: Profile 5 (single-layer, streaming-focused) | Statement: [Dolby Vision, profileExample, Profile 5 (single-layer, streaming-focused)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: profileExample Context triple: [Dolby Vision, profileExample, Profile 5 (single-layer, streaming-focused)]
-
A.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
-
B.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
C.
typicalProfile
chosen
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
academicProfile
Indicates the relationship that captures an entity’s academic background, qualifications, and scholarly activities or achievements.
-
E.
recruitingProfile
Indicates that an entity serves as or is associated with a recruiting profile used for hiring or talent acquisition activities.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c88f608190bf734e0b744bf3d1 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.