Triple
T37480157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV1 |
E931391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ultra-high-definition television format |
C8830
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ultra-high-definition television format Context triple: [UHDTV1, instanceOf, ultra-high-definition television format]
-
A.
high-definition video format
chosen
A high-definition video format is a digital video standard that delivers significantly higher resolution, clarity, and detail than standard-definition formats, typically including 720p, 1080p, or higher resolutions.
-
B.
high-definition television feed
A high-definition television feed is a digital video and audio signal that delivers television content at significantly higher resolution and clarity than standard-definition broadcasts.
-
C.
HDR video standard
An HDR video standard is a specification that defines how to capture, encode, transmit, and display video with an extended range of brightness and color to produce more realistic and detailed images than standard dynamic range formats.
-
D.
television format
A television format is a structured blueprint for a TV program, defining its core concept, rules, narrative style, and production elements so it can be reproduced or adapted across different episodes, seasons, or markets.
-
E.
4K and higher resolution display
A 4K and higher resolution display is a screen capable of rendering images at approximately 3840×2160 pixels or more, providing exceptionally sharp detail and clarity for visual content.
- F. None of above.
Provenance (1 batch)
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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.