Triple
T37537873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV2 |
E933254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television broadcast format |
C4924
|
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: television broadcast format Context triple: [UHDTV2, instanceOf, television broadcast format]
-
A.
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.
-
B.
broadcast television standard
chosen
A broadcast television standard is a defined set of technical specifications and protocols that govern how video and audio signals are encoded, transmitted, and received for over-the-air television broadcasting.
-
C.
broadcast television system
A broadcast television system is an integrated network of equipment, standards, and transmission channels that captures, encodes, and distributes audiovisual content over the air or via cable/satellite to multiple receivers simultaneously.
-
D.
analog television standard
An analog television standard is a technical specification that defines how video and audio signals are encoded, transmitted, and displayed using continuous (non-digital) waveforms for broadcast television.
-
E.
television broadcast package
A television broadcast package is a cohesive set of visual and audio elements—such as intros, lower thirds, transitions, and graphics—designed to create a unified on-air identity for a TV program or channel.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.