Triple
T4544300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nippon Television Network |
E110010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | terrestrial television network |
C3769
|
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: terrestrial television network Context triple: [Nippon Television Network, instanceOf, terrestrial television network]
-
A.
television network
chosen
A television network is an organization that produces, acquires, schedules, and distributes television programming across multiple stations or platforms under a unified brand.
-
B.
commercial television network
A commercial television network is a broadcast organization that distributes television programming to affiliated stations and audiences, primarily funded by advertising revenue and designed to attract large viewership for profit.
-
C.
public television network
A public television network is a broadcast organization funded primarily by public sources that provides educational, cultural, and informational programming in the public interest rather than for commercial profit.
-
D.
cable television network
A cable television network is an organization that creates, aggregates, and distributes television programming via cable infrastructure to subscribers, managing content schedules, advertising, and affiliate relationships.
-
E.
digital terrestrial television platform
A digital terrestrial television platform is a system that delivers multiple digital TV and radio services over terrestrial broadcast frequencies to compatible receivers, often including interactive and on-demand features.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.